Convene 20 agentic specialists on your hardest engineering problems.
Distinct perspectives, unified design, actionable plans, every decision tracked. Ships sibling councils for finance, people, and revenue under their own slash commands.
Skills 66 in the Claude listing
A11y audit Use when auditing accessibility compliance of a feature or codebase. Adr template Use when recording significant architectural or design decisions that affect the system. Ai evaluation Use when designing an evaluation framework for AI/LLM features. Analytics design Use when planning measurement strategy for a feature or product area. Api design Use when designing REST or RPC endpoint contracts with request/response types and error handling. Audit trail design Use when designing audit logging systems for accountability and compliance evidence. Caching strategy Use when designing or auditing a caching architecture. Changelog design Use when preparing release changelogs, migration guides, or breaking change communication for consumers. Codebase context Use when analyzing an existing codebase for architecture, tech stack, conventions, and infrastructure. Competitive analysis Use when designing features that exist in competing products or analyzing prior art in the market. Compliance review Use when reviewing proposed features and data flows against GDPR, CCPA, HIPAA, and other privacy regulations. Cost analysis Use when modeling infrastructure costs, projecting scaling expenses, or identifying optimization opportunities across cloud providers and third-party services. Crypto review Use when reviewing cryptographic implementations for algorithm choice correctness, key management soundness, side-channel resistance, and crypto agility readiness. Data classification Use when classifying data elements by sensitivity tier and defining per-tier handling requirements. Deployment plan Use when designing deployment strategies including environment progression, CI/CD pipelines, zero-downtime releases, rollback procedures, and feature flag management. Design system architecture Use when designing a token-based design system architecture. Device integration Use when designing integration strategies for device hardware APIs including camera, sensors, biometrics, and Bluetooth. Distributed patterns Use when designing distributed systems or evaluating distributed architecture patterns. Documentation plan Use when designing documentation architecture for a project or team. E2e testing Use when designing end-to-end test suites, visual regression testing, or cross-browser test strategies. Edge case enumeration Use when systematically discovering edge cases for proposed features using structured enumeration techniques. Embedded architecture Use when designing firmware architecture for embedded or IoT devices. Enterprise search strategy Use when the council needs to surface organizational knowledge buried across multiple internal sources (wikis, design docs, ADRs, past tickets, postmortems, chat archives, code repos). Failure mode analysis Use when systematically identifying failure scenarios for proposed features and infrastructure changes. Finance close checklist Use when orchestrating monthly or quarterly close. Finance controls audit Use when testing a SOX 404 control or designing a controls walkthrough. Finance journal entries Use when constructing a GAAP/IFRS journal entry from facts. Finance reconciliation Use when reconciling a balance-sheet account during the close cycle. Finance tax research Use when answering a federal, state, or international tax question that requires authoritative research. Finance variance analysis Use when explaining actual-vs-plan or actual-vs-prior variance with commentary. Finops analysis Use when analyzing cloud spending, cost attribution, or unit economics. Fleet management Use when designing fleet management infrastructure for IoT device fleets. Formal spec Use when writing formal specifications in TLA+ to verify system properties, defining state variables, configuring TLC model checker, and documenting assumptions and limitations. Growth engineering Use when designing growth infrastructure including onboarding funnels, referral mechanics, A/B test instrumentation, and re-engagement loops. Hw sw boundary Use when reviewing the hardware/software security interface to verify hardware security feature enablement, IOMMU/SMMU DMA protection configuration, and HW/SW trust model coherence. I18n review Use when reviewing internationalization readiness of a feature or codebase. Impact estimation Use when comparing multiple features or initiatives to determine prioritization order. Interaction design Use when designing component interaction specs with visual states, transitions, and accessibility requirements. Invariant analysis Use when enumerating security claims from a design, formalizing them as invariants, checking for hidden assumptions, and assessing verification feasibility. Isolation review Use when mapping isolation boundaries, enumerating crossing points, verifying enforcement mechanisms, and testing for bypass paths across trust domains. Journey mapping Use when mapping complete user journeys through multi-step flows, onboarding sequences, or feature workflows. Kernel hardening Use when auditing kernel security configuration for memory protection, syscall surface reduction, control flow integrity, and integrity mechanisms against local and remote attack vectors. Library evaluation Use when adding new packages, choosing between dependency alternatives, or auditing existing libraries. Load modeling Use when planning capacity or projecting infrastructure needs under growth. Messaging strategy Use when developing product messaging frameworks including value propositions, feature naming, microcopy guidelines, and CTA strategy. Ml workflow Use when designing end-to-end ML workflows. Monetization design Use when designing monetization architecture including pricing tiers, paywall placement, subscription infrastructure, and upgrade flows. Motion design Use when designing the motion language for a feature or system. Mvp scoping Use when defining minimum viable scope for a product or feature launch. Navigation design Use when designing navigation architecture for mobile or cross-platform features including screen hierarchy, deep linking schemes, and state preservation strategies. Observability design Use when designing monitoring, alerting, logging, tracing, and SLI/SLO strategies for services or systems. Pattern analysis Use when auditing codebase patterns or evaluating proposed changes for convention consistency. Performance audit Use when profiling application performance or diagnosing slow page loads. Pipeline design Use when designing data pipelines for moving, transforming, and delivering data. Platform audit Use when auditing a feature or implementation against platform-specific guidelines such as iOS HIG, Material Design 3, and WCAG. Pqc readiness Use when assessing a system's readiness for post-quantum cryptography migration, inventorying classical crypto usage, mapping NIST-standardized PQC replacements, and planning phased migration timeline Prompt engineering Use when designing, evaluating, or versioning system prompts for LLM-powered features. Protocol analysis Use when analyzing cryptographic protocol security by modeling state machines, enumerating transitions, and identifying desynchronization, replay, downgrade, and session binding vulnerabilities. Protocol design Use when selecting and designing communication protocol stacks for IoT or embedded systems. Rag architecture Use when designing a Retrieval-Augmented Generation pipeline. Schema design Use when designing or modifying database schemas with migration plans. Schema evaluation Use when evaluating or designing data warehouse schemas for analytical workloads. Technology radar Use when evaluating frameworks, tools, or platforms for adoption, migration, or stack decisions. Testing strategy Use when designing test plans for new features or improving existing test coverage. Threat model Use when applying STRIDE threat modeling to identify security risks in proposed features. Visual audit Use when performing structured visual design critique of an interface.