Results for “design-implementation”

Create an icon system specification covering grid, sizing, naming, categories, and implementation guidance.

Enforces system design, project structure, dependency management, error handling, testing, and documentation standards at principal-engineer level.

Writes mechanism-first technical implementation deep-dive articles that explain design intent, data flow, trade-offs, and operations, with code locations as supporting evidence.

Creates detailed, step-by-step implementation plans from specs or requirements, with task decomposition, file structure, and test-driven development instructions.

Design APIs with endpoints, methods, and documentation. TRIGGERS - Use when user needs help with api-design related tasks.

Load this skill when the user says "verify-implementation", "verify implementation", or "/verify-implementation". Reviews the implementation against the issue requirements and project coding standards, runs automated checks, and produces a gated report before acceptance criteria are ticked off.

Builds a feature specification from scratch through a relentless, evidence-based interview that walks the design tree decision-by-decision, resolving dependencies as it goes. Use when the user wants to plan, design, scope, specify, or flesh out a new feature, capability, or system behavior before implementation. Produces a feature specification focused on system behaviors, not implementation detail. Does not refine or stress-test an existing plan — use iterative-plan-review. Does not document already-built features — use project-documentation. Does not design the contract for an interface — use design-an-api. Does not research open-ended options before there is a feature to specify — use research.