Loading...
Loading...
Found 29 Skills
Design PM-friendly technical architecture for features. No code, only high-level design decisions.
Clarify and compile project technical solutions. Use this when users need to determine the overall implementation approach, key technology trade-offs, module and file responsibilities, compatibility and verification boundaries for a problem, bug, function change, or existing requirement in combination with the current project, or when they need to create a technical document that can be understood by product, development, and testing teams and used for subsequent work. No prior requirement document is required, and it does not cover task breakdown, coding implementation, or project acceptance.
Run /architect when choosing between approaches, designing a feature or page, picking a tech stack, or when /develop says a decision is owed, anytime a load bearing technical decision is unmade. Asks deep questions, recommends an answer, and writes a build spec to docs/specs/. Owns all spec files.
Technical Design - picks one variant per problem area from the research catalogue, then produces architecture diagrams, interfaces, and data flow. Decisions live here, not in research.
Create a light-mode technical design system with warm paper surfaces, dark outer framing, subtle diagonal texture, precise bracketed geometry, and restrained accent signals.