Automated summary
Implements a production change inside an existing repository, following its patterns and conventions, with or without new test coverage.
Strengths
- Routes to /tdd only when a test-first flow is justified, without forcing it on every task.
- Requires reading the relevant code and respecting the repo's architecture and conventions before introducing new structure.
- Structures the end of the task: running the fitting checks (lint, types, tests, builds) then summarizing affected files and recommending the next step (/review or /draft-pr).
- Asks for the spec path, or otherwise clarifies scope and success criteria before writing code.
Limitations
- Assumes a repo already set up with defined personas (subagents/developer.md) and the related commands.
- Provides no language- or framework-specific verification checklist: choosing the right checks is left to the developer.
- Does not cover review, PR creation, or commits: it only recommends those as next steps.
For implementing a feature or fix that is already scoped in an existing repository while staying consistent with its patterns.
When the task is primarily about writing new tests (use /tdd) or analyzing an existing diff (use /review).
Security analysis
SafeThe skill contains only workflow guidance for implementing code changes. It declares no tools and does not instruct destructive commands, secret exfiltration, obfuscated payloads, or safety bypasses.
No concerns found
How this analysis is madeExamples
Implement the billing retry logic described in docs/specs/billing-retry.md, following the existing patterns in the payments service.Add a --dry-run flag to the export CLI command. No new tests needed here — follow the current option-handling conventions and run lint, types and the test suite./code — add rate limiting middleware to the public API, reusing the existing Redis client and config patterns.name: code description: Implement production changes with or without new test coverage.
Code
Invocation
This skill is performed in the Developer persona. If you are not already running as Developer (for example, the user invoked /code directly), read subagents/developer.md and adopt its role guidance for the rest of this task. Stay in the current chat—do not delegate to a subagent.
Objective
Implement the requested change using existing project patterns. This skill covers spec-driven feature work and implementation tasks that are not primarily about new automated tests.
Instructions
- Ask for the spec path when the work is spec-driven. If there is no spec, clarify the requested scope and success criteria.
- Determine whether the change should be test-first:
- if yes, route to
/tddbefore implementation - if not, continue here
- if yes, route to
- Read the relevant code paths and follow existing patterns before introducing new structure.
- Follow the repo's established architecture and conventions.
- Implement the smallest coherent change that satisfies the task.
- Run the verification checks that fit the change (linting, type checking, tests, builds, etc.).
- Summarize the implementation, affected files, checks run, and recommended next step (
/reviewor/draft-pr).
Notes
coderemains distinct from/tddbecause some implementation work in this repo does not justify a test-first flow.- When opening a PR or preparing a review, treat your base branch as the comparison target.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/code-ms47vp6w/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/code-ms47vp6w' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/code-ms47vp6w/download' --output '.skill-downloads/code-ms47vp6w/SKILL.md.part' && mv '.skill-downloads/code-ms47vp6w/SKILL.md.part' '.skill-downloads/code-ms47vp6w/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/code-ms47vp6w/SKILL.md' && test -s '.skill-downloads/code-ms47vp6w/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/code' && cp -R '.skill-downloads/code-ms47vp6w' '.claude/skills/code'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/code-ms47vp6w'openskills read 'code-ms47vp6w'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/code-ms47vp6w/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.