architecture-analysis
Map frameworks, build tools and architectural patterns before changing a line.
Twenty-one reusable skills for understanding code, planning projects and shipping reliable changes.
Search by name, problem or output. Filter only when you need to narrow the field.
Map frameworks, build tools and architectural patterns before changing a line.
Find unused packages, hidden risk, circular imports and cleanup opportunities.
Generate tests that match the project’s framework, patterns and conventions.
Turn backend contracts into project-aware requests, types, mocks and tests.
Pressure-test a PRD against five engineering quality gates before build starts.
Extract credible, interview-defensible project experience from real code.
Package architecture, risk and operating context for the next project owner.
Create practical usage documentation grounded in source code evidence.
Plan and drive old-to-new migrations with phases, checks and rollback control.
Route each review or refactor to the Clean Code rule that matters most.
Chain multiple skills into a traceable, validated end-to-end workflow.
Analyze changes, bump versions and keep bilingual release notes in sync.
Bake a repeatable multi-skill pipeline into one dedicated workflow skill.
Move from requirement intake to engineering-ready specification with evidence.
Systematically learn a library, framework or codebase from first principles.
Convert existing documents into a focused, reusable agent capability.
Take a raw idea through evidence, users, value, scope and solution design.
Compress verbose prompts while preserving meaning, behavior and constraints.
Expose ambiguity through a structured interview before a prompt is executed.
Keep critical operating instructions visible across long-running work.
Turn durable engineering conventions from conversation into project rules.
Each skill defines how the agent reads context, makes decisions and produces work your team can review.
Understand the project, available evidence and constraints before proposing a change.
Use a deliberate sequence with clear quality standards and safe operating boundaries.
Produce something the team can use, review and improve after the conversation ends.
Install all 21 skills, then invoke the one that matches the work.