Use to implement or review software with minimal code and proportional checks.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this skill for software implementation, fixes, refactoring, infrastructure, tests, and technical review. In mixed work, treat the approved design as fixed input and apply this skill only to implementation.
Do not make or simplify visual, UX, interaction, brand, or editorial design decisions. Do not reduce design quality to save code.
Understand the affected flow before choosing a change. Prefer an existing pattern, the standard library, native platform features, or an installed dependency. Add only the code that the current requirement needs. Avoid speculative abstractions, compatibility layers, configuration, and extension points.
For a bug, find the root cause and inspect relevant callers. Fix a shared cause when the evidence supports that scope.
Use the smallest evidence that proves the result. Prefer an existing relevant test, focused command, build, type check, linter, temporary probe, or direct behavior check. Run broader checks when the changed scope, risk, repository rules, or CI behavior requires them.
Add a persistent test when it protects a likely repeat failure, stable public contract, non-obvious logic, or high-impact behavior. Static and trivial edits usually need direct inspection only.
Do not simplify away security controls, trust-boundary validation, data-loss protection, required error handling, accessibility, or an explicit requirement. Match the proof to the impact, uncertainty, and recovery cost.
Keep the handoff short. State the change, the evidence, and any known limit that affects the user's decision.
Related skills: vibe-coding (dev-toolkit) covers broader AI-assisted
development, and verification-before-completion (superjawn) covers final
proof before a completion claim.
Credit: Adapted from DietrichGebert/ponytail under the MIT license.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Scholarly writing and research compliance. Use for CRediT, preregistration, Plan S, Nelson Memo, preprints, ORCID, LLM disclosure.
The English summary is being prepared. Showing the original description.
Web accessibility patterns for news and academic sites. Use for WCAG audits, alt text, accessible data viz, and assistive tech.
The English summary is being prepared. Showing the original description.
Eliminates AI-generated writing patterns that erode reader trust. Use when writing or editing articles, docs, or press releases.
The English summary is being prepared. Showing the original description.
API hardening for Express, FastAPI, and serverless. Use for rate limiting, CORS, input validation, API keys, or OWASP API Top 10.
The English summary is being prepared. Showing the original description.
Explores intent and design before implementation. MUST use before creating or modifying any feature, component, or behavior.
The English summary is being prepared. Showing the original description.
Public records requests under Brazil's Access to Information Law (LAI). Use for Fala.BR filings, e-SIC, and CGU/CMRI appeals.
The English summary is being prepared. Showing the original description.