This skill should be used when writing Architecture Decision Records (ADRs), documenting technical decisions, or reviewing architecture choices. Triggers on phrases like "document this decision", "create ADR", "architecture decision", "why did we choose", "record the decision", "MADR template", or when the user is working on plan files that contain ADR sections.
Production-grade AI architecture patterns for enterprise - security, governance, scalability, and operational excellence
Create controller classes with dependency injection that expose clean public interfaces for use cases following clean architecture patterns.
Project-specific code patterns for Server Actions, data fetching, error handling, file organization. Use when implementing features to follow established patterns, or when user asks about project conventions/patterns/architecture.
Understand computer systems from digital logic through operating systems, networks, databases, and distributed systems.
Load architecture principles and core conventions for grounding work against project standards - simple context loading for all workflow stages
Understand the defense-in-depth security architecture of Secure Vibe Coding OS. Use this skill when you need to understand the overall security approach, the 5-layer security stack, OWASP scoring, or when to use other security skills. Triggers include "security architecture", "defense in depth", "security layers", "how does security work", "OWASP score", "security overview", "security principles".
Engineer SSR caching strategies that preserve correctness under concurrent updates and streaming.
Common Solidity design patterns and implementations for secure smart contract development. Use when implementing standard functionality like access control, upgradeability, or token standards.
Guides structured evaluation of design options with trade-off analysis. Use this skill when choosing architectures, selecting technologies, evaluating implementation approaches, or making design decisions.
Plan and review architecture decisions via a structured interview and ADR output. Use when choosing between system design alternatives.
Prevent feature creep when building software, apps, and AI-powered products. Use this skill when planning features, reviewing scope, building MVPs, managing backlogs, or when a user says "just one more feature." Helps developers and AI agents stay focused, ship faster, and avoid bloated products.
Execute high-density analysis on complex ideas/tasks. Move from 'Vague' to 'Verified' by producing: constraints -> core modules -> facts vs assumptions -> ASCII flow maps (boundary + critical path) -> latticework lens sweep -> micro->macro causal chains -> pre-mortem failure modes. Use when analyzing system architecture, validating technical ideas, or decomposing a thorny problem before designing solutions.
This skill should be used when the user asks about "decision drivers", "architectural forces", "quality attributes", "how to identify trade-offs", "non-functional requirements for ADRs", or needs help identifying, documenting, and weighing the forces that influence architectural decisions.
Provides startup advice using Eric Ries' Lean Startup methodology focusing on Build-Measure-Learn cycles, validated learning, and rapid experimentation. Use when advising on MVPs, product iterations, pivot decisions, growth metrics, or when user mentions Lean Startup, Eric Ries, validated learning, or rapid experimentation.
Provides ruthless prioritization framework for product decisions. Use when advising what to build next, challenging feature ideas, evaluating new features against Impact vs Effort matrix, applying stage-based rules (pre-launch, post-launch, growth), or keeping roadmaps focused by filtering feature creep. Enforces retention-first mindset and validates features against real user needs versus imaginary requirements.
Assess technical patterns, integrations, and constraints in the domain to inform feasibility and strategy.
Elite execution & breakthrough perfection framework. Think like a human, execute like a master across all technical domains.
Use when cataloging technical debt under time pressure and tempted to explain choices instead of delivering document - enforces execution discipline with scoped delivery patterns for partial catalogs
Product Owner & App Journey Architect role skill. Use when Claude needs to act as a seasoned product owner who translates business goals into clear, actionable product requirements; identifies gaps, ambiguities, and hidden assumptions; designs and documents user journeys, system flows, and state diagrams using Mermaid; reviews high-level designs for completeness and feasibility; uncovers edge cases, failure scenarios, and error-handling strategies; and validates specifications are build-ready. Triggered by requests to review product specs, design user journeys, create system flows, challenge requirements clarity, identify design gaps, or architect application flows.
This skill provides guidance for creating feature specifications in the Spec-Driven Development process.
Micro-task development patterns with 50% context budget. Use for task decomposition, context management, escape hatch protocols, and orchestration patterns.
Analyze project briefs to resolve architectural ambiguity before tech stack selection. Determines greenfield vs brownfield, platform constraints, integration requirements, scale expectations, and team context. Produces architecture-context.json for downstream skills.
