product-factory/architecture
Apply this skill whenever designing, scaffolding, reviewing, or refactoring the architecture of a Next.js App Router + TypeScript + Tailwind + shadcn + Drizzle application. Triggers on requests like "how should I structure this", "where should this logic live", "scaffold a new feature", "review my folder structure", "plan this feature", "add a new module", or any time you're creating multiple files that need to fit together coherently. Use this skill proactively — do not make ad-hoc structural decisions without consulting it.
90
Quality
90%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description with excellent trigger term coverage and clear when-to-use guidance. The main weakness is that the 'what' portion describes general architectural activities rather than specific concrete actions the skill enables. The tech stack specificity and explicit trigger phrases make it highly distinctive and actionable.
Suggestions
Add 2-3 specific concrete actions like 'organize route groups', 'structure Drizzle schemas', or 'scaffold feature modules with proper colocation' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Next.js App Router + TypeScript + Tailwind + shadcn + Drizzle) and lists general actions (designing, scaffolding, reviewing, refactoring architecture), but doesn't list specific concrete actions like 'create route handlers', 'organize API endpoints', or 'structure database schemas'. | 2 / 3 |
Completeness | Clearly answers both what (designing/scaffolding/reviewing/refactoring architecture for a specific tech stack) and when (explicit trigger phrases plus the condition 'any time you're creating multiple files that need to fit together coherently'). Includes explicit 'Use this skill proactively' guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger phrases users would actually say: 'how should I structure this', 'where should this logic live', 'scaffold a new feature', 'review my folder structure', 'plan this feature', 'add a new module'. These are realistic user queries. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific tech stack combination (Next.js App Router + TypeScript + Tailwind + shadcn + Drizzle) and focus on architectural/structural decisions. Unlikely to conflict with general coding skills or individual technology skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality architecture skill that efficiently communicates stack conventions, folder structure, and decision rules with concrete, executable examples. The content respects Claude's intelligence and provides actionable guidance. The main gap is the lack of explicit validation workflows for multi-step operations like scaffolding features or running migrations.
Suggestions
Add a 'Scaffolding a New Feature' workflow section with explicit steps and validation checkpoints (e.g., 1. Create feature folder, 2. Add schema.ts with Zod validation, 3. Verify types compile, 4. Add actions.ts, etc.)
Include a brief migration workflow for Drizzle: generate → review SQL → apply → verify, with explicit validation between steps
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables for quick reference, minimal prose, and code examples that demonstrate patterns without explaining concepts Claude already knows (like what TypeScript or Tailwind are). | 3 / 3 |
Actionability | Provides fully executable code examples throughout (Server Components, Server Actions, query key factories, Drizzle schemas), concrete decision rules in table format, and copy-paste ready patterns for common scenarios. | 3 / 3 |
Workflow Clarity | Decision rules table provides clear guidance for where things go, but lacks explicit validation checkpoints or feedback loops for multi-step processes like scaffolding a new feature or adding a new module. The 'New DB table' row mentions drizzle-kit generate but doesn't show a validate-then-proceed workflow. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections (Stack Identity, folder structure, decision rules, anti-patterns). For a skill of this scope, the single-file format with logical sections is appropriate—no unnecessary nesting or references to external files that would fragment the guidance. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Install with Tessl CLI
npx tessl i product-factory/architectureReviewed
Table of Contents