Principal-level product development and architecture skill for modern professional web platforms. Covers advanced frontend engineering, Next.js App Router patterns, React component architecture, React Hook Form, state management, system design, Firebase auth/session, and long-term platform stewardship.
SkillScore82Maintained
Automatic
◆Frontend / UI pack
Last verified 8/8/2026
What it changes
Passed 18 of 22 test cases with the skill, and 14 of 22 without it.
Without skill64%
With skill82%
Checks it passed that the model alone missed
Contains zero comment lines in the file.
Types caught errors as unknown rather than any.
Contains zero comment lines in the code snippets.
and 5 more in the full report
5 fixed13 passed either way3 still failing1 broke
Pass-rate lift
+18 pp
Tokens
+649%
Agent turns
0%
Response time
-14%
Model gemini-3.6-flashMeasured 8/8/2026v1 · latest is v218 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
Sistemimizde kullanıcıların hazırladığı CV metinlerini alıp ATS analizi yapmak üzere işleyen bir Next.js App Router POST API route handler yazmanı istiyorum. İstek gövdesini doğrulamalı, oturum kontrolü yapmalı, servise yönlendirmeli ve olası hataları ele alıp istemciye uygun JSON yanıtı dönmelidir. Kod örneğini ve klasör içi yerleşim mantığını açıklayarak sun.
What was checked, without and with the skill
Checked
Without skill
With skill
Does not contain any inline or block comment lines in the code snippets.
Missed
Passed
Invokes requireAuth from `@/lib/server/auth` on the first line of execution.
Missed
Passed
Places the feature server code inside `src/features/ats/server/`.
Missed
Passed
case-01 · gemini-3.6-flash · 8/8/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md58 linessingle file
Senior Software Architect
Provide architecture guidance grounded in the actual system, constraints, and business goals. Preserve project conventions unless changing them produces a demonstrated benefit.
Establish Context
Inspect the current architecture before proposing a target state. Determine:
system purpose, users, critical journeys, and service levels;
repository boundaries, runtime topology, deployment model, and ownership;
data sources, consistency needs, privacy classification, and retention;
integrations, failure domains, trust boundaries, and operational constraints;
expected scale, team capability, delivery horizon, and migration tolerance.
Do not assume a framework, cloud, database, directory layout, or architectural style that the project has not chosen.
Make the Decision Explicit
Frame architecture work as a decision rather than a diagram exercise:
State the problem, forces, and non-goals.
Identify viable options, including keeping the current design.
Compare options using the constraints that matter: simplicity, delivery cost, operability, reliability, performance, security, reversibility, and team fit.
Recommend the smallest design that satisfies current requirements and preserves an acceptable evolution path.
Record consequences, assumptions, risks, and signals that would justify revisiting the decision.
Use an Architecture Decision Record when a choice is cross-cutting, costly to reverse, or likely to be questioned later.
Design Across Boundaries
Cover only the views needed by the task:
context and ownership boundaries;
components or services and their responsibilities;
synchronous and asynchronous interactions;
data ownership, lifecycle, schemas, and migration strategy;
authentication, authorization, secrets, and trust boundaries;
capacity, latency budgets, caching, backpressure, and failure handling;
observability, deployment, rollback, recovery, and operational ownership.