Guidelines
akash-network/node
Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.
A skill your agent uses when a complex or risky code change should be split into Kent Beck's two-step method by first making the change easy through behavior-preserving preparatory refactoring, then…
Install 051 Design Two Steps Methods
$ npx skills add jabrena/plinth --skill 051-design-two-steps-methods -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jabrena/plinth 051-design-two-steps-methods --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/051-design-two-steps-methods .claude/skills/051-design-two-steps-methods && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "051-design-two-steps-methods" agent skill from https://github.com/jabrena/plinth/tree/main/skills/051-design-two-steps-methods into .claude/skills/051-design-two-steps-methods/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "051-design-two-steps-methods", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jabrena/plinth/tree/main/skills/051-design-two-steps-methodsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jabrena/plinth --skill 051-design-two-steps-methods -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jabrena/plinth 051-design-two-steps-methods --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/051-design-two-steps-methods .agents/skills/051-design-two-steps-methods && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "051-design-two-steps-methods" agent skill from https://github.com/jabrena/plinth/tree/main/skills/051-design-two-steps-methods into .agents/skills/051-design-two-steps-methods/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "051-design-two-steps-methods", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jabrena/plinth --skill 051-design-two-steps-methods -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jabrena/plinth 051-design-two-steps-methods --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/051-design-two-steps-methods .cursor/skills/051-design-two-steps-methods && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "051-design-two-steps-methods" agent skill from https://github.com/jabrena/plinth/tree/main/skills/051-design-two-steps-methods into .cursor/skills/051-design-two-steps-methods/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "051-design-two-steps-methods", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jabrena/plinth.git --path skills/051-design-two-steps-methods--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jabrena/plinth --skill 051-design-two-steps-methods -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jabrena/plinth 051-design-two-steps-methods --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/051-design-two-steps-methods .gemini/skills/051-design-two-steps-methods && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "051-design-two-steps-methods" agent skill from https://github.com/jabrena/plinth/tree/main/skills/051-design-two-steps-methods into .gemini/skills/051-design-two-steps-methods/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "051-design-two-steps-methods", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jabrena/plinth 051-design-two-steps-methodsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jabrena/plinth --skill 051-design-two-steps-methods -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/051-design-two-steps-methods .github/skills/051-design-two-steps-methods && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "051-design-two-steps-methods" agent skill from https://github.com/jabrena/plinth/tree/main/skills/051-design-two-steps-methods into .github/skills/051-design-two-steps-methods/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "051-design-two-steps-methods", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jabrena/plinth --skill 051-design-two-steps-methods -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jabrena/plinth 051-design-two-steps-methods --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/051-design-two-steps-methods .opencode/skills/051-design-two-steps-methods && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "051-design-two-steps-methods" agent skill from https://github.com/jabrena/plinth/tree/main/skills/051-design-two-steps-methods into .opencode/skills/051-design-two-steps-methods/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "051-design-two-steps-methods", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
051-design-two-steps-methods- GitHub stars
- 447
- Token cost
- ~973 tokens
- SKILL.md length
- 436 words
- Files
- 2 (incl. references)
- Skills in repo
- 124
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when a complex or risky code change should be split into Kent Beck's two-step method by first making the change easy through behavior-preserving preparatory refactoring, then…
- Then making the intended behavior change once the design supports it
- SKILL.md covers Constraints, When to use this skill, Workflow and Reference
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Requests such as Apply two-step change
What it does
051 Design Two Steps Methods is an agent skill from jabrena/plinth. Use when a complex or risky code change should be split into Kent Beck's two-step method by first making the change easy through behavior-preserving preparatory refactoring, then making the intended behavior change once the design supports it. This should trigger for requests such as Apply two-step change; Make this risky change safer; Refactor before changing behavior; Separate preparation from behavior change. Part of Plinth Toolkit
Its SKILL.md is about 970 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/051-design-two-steps-methods.md`).
It sits in Development, covering Refactoring. The repository describes itself as: Plinth is an AI-native engineering toolkit for modern Java enterprise SDLC, built around reusable Commands, Agents, Skills, and MCP Servers. The licence is Apache-2.0.
When your agent uses it
- Then making the intended behavior change once the design supports it
- Requests such as Apply two-step change
- Make this risky change safer
- Refactor before changing behavior
Example prompts
- “/051-design-two-steps-methods”
What it can do on your machine
Read from SKILL.md and the folder at commit dca88dc. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
051 Design Two Steps Methods loads about 973 tokens when it runs, and up to ~2.6k if it reads all its reference files. Until then it costs about 117 tokens; SKILL.md has 436 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jabrena/plinth at commit dca88dc, republished under its Apache-2.0 licence (© jabrena). 436 words, ~973 tokens.
Download SKILL.mdSave it as
.claude/skills/051-design-two-steps-methods/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- 051-design-two-steps-methods
- description
- Use when a complex or risky code change should be split into Kent Beck's two-step method by first making the change easy through behavior-preserving preparatory refactoring, then making the intended behavior change once the design supports it. This should trigger for requests such as Apply two-step change; Make this risky change safer; Refactor before changing behavior; Separate preparation from behavior change. Part of Plinth Toolkit
- license
- Apache-2.0
- metadata.author
- Juan Antonio Breña Moral
- metadata.version
- 0.19.0
Two-Step Change Method
Guide Java developers through complex or risky changes by keeping design preparation separate from behavior modification. This is an interactive SKILL.
What is covered in this Skill?
- Clarifying the intended behavior change before editing
- Identifying design obstacles that make the change difficult or risky
- Step 1: behavior-preserving preparatory refactoring that makes the change easy
- Validation that Step 1 preserves existing behavior
- Step 2: the smallest intended behavior change after the design supports it
- Verification that Step 2 delivers the intended behavior
- Handoff to focused Java, framework, persistence, messaging, API, or testing skills while preserving the two-step sequence
Constraints
Separate behavior-preserving preparation from behavior-changing work, and validate after each step.
- MUST: State the intended behavior change before proposing preparatory refactoring
- MUST: Keep Step 1 behavior-preserving; do not mix broad refactoring with the intended behavior change
- MUST: Verify existing behavior after Step 1 using the project-appropriate tests, build, characterization tests, or manual checks
- MUST: Make Step 2 only after the design has been prepared and validated
- MUST: Verify the intended behavior after Step 2 with focused tests and relevant build checks
- MUST: Record assumptions and risks when preparation cannot be fully separated from behavior change
When to use this skill
- Apply two-step change
- Make this risky change safer
- Refactor before changing behavior
- Separate preparation from behavior change
- Make the change easy, then make the easy change
Show full SKILL.md (209 more words)Show less
Workflow
- Define the intended change
Read references/051-design-two-steps-methods.md, inspect the relevant code and tests, and state the exact behavior or capability that must change. Identify why the current design makes the change complex, risky, or hard to verify.
- Plan preparatory refactoring
Choose the smallest behavior-preserving refactoring that reduces the obstacle: extract method or class, clarify names, isolate dependencies, add seams for testing, move responsibilities, improve types, or add characterization tests before touching behavior.
- Make the change easy
Apply Step 1 as focused preparatory refactoring only. Keep commits, notes, or task boundaries clear enough that reviewers can see no intended behavior change is included.
- Validate preserved behavior
Run the relevant existing tests, build checks, characterization tests, or manual verification. If behavior changes unexpectedly, fix or revert the preparation before proceeding.
- Make the easy behavior change
Apply the smallest intended behavior change now that the design supports it. Use focused Java, framework, persistence, messaging, API, or testing skills when detailed implementation guidance is needed.
- Verify and report the outcome
Verify the intended behavior with targeted tests and relevant project validation. Report what was preparation, what changed behavior, what was verified after each step, and any remaining risks.
Reference
For detailed guidance, examples, and constraints, see references/051-design-two-steps-methods.md.
© jabrena, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/051-design-two-steps-methods of jabrena/plinth.
- SKILL.md
- references/051-design-two-steps-methods.md
Open the folder on GitHubat commit dca88dc
Compare with similar skills
051 Design Two Steps Methods next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| 051 Design Two Steps Methods this skilljabrena/plinth | 447 | — | ~973 | Automated safety check: Pass | Apache-2.0 | |
| Guidelinesakash-network/node | 1.1k | 20 repos | ~577 | Automated safety check: Pass | MIT | |
| Component Refactoringlangflow-ai/langflow | 155k | — | ~3.5k | Automated safety check: Pass | MIT | |
| Migrate Core Code to Submodulestinyhumansai/openhuman | 42k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| ast-grep Structural Searchcode-yeongyu/oh-my-openagent | 70k | — | ~3.3k | Automated safety check: Pass | MIT | |
| Systematic Code Refactoringluongnv89/claude-howto | 42k | — | ~3k | Automated safety check: Pass | MIT |
Similar skills
Component Refactoring
langflow-ai/langflow
Refactor high-complexity React components in Langflow frontend.
Migrate Core Code to Submodules
tinyhumansai/openhuman
Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.
ast-grep Structural Search
code-yeongyu/oh-my-openagent
Searches and rewrites code by syntax-tree shape across 25 languages with ast-grep, for codemods, structural queries and YAML lint rules, using a Python wrapper script.
Systematic Code Refactoring
luongnv89/claude-howto
Guides refactoring in phases based on Martin Fowler's method: research, test coverage check, planning and small tested steps, with your approval at each phase.
Codex
skills-directory/skill-codex
A skill your agent uses when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex for code analysis, refactoring, or automated editing
More from jabrena/plinth
All 124 skills in this repo703 Technologies Fuzzing Testing
jabrena/plinth
A skill your agent uses when you need to add or review fuzz testing for Java APIs with CATS — including contract-driven negative testing, malformed payload validation, boundary input exploration, CI…
033 Architecture Diagrams
jabrena/plinth
A skill your agent uses when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, UML Deployment Diagrams…
112 Java Maven Plugins
jabrena/plinth
A skill your agent uses when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning…
151 Java Performance Jmeter
jabrena/plinth
A skill your agent uses when you need to set up JMeter performance testing for a Java project — including creating the run-jmeter.sh script from the exact template, configuring load tests with…
161 Java Profiling Detect
jabrena/plinth
A skill your agent uses when you need to set up Java application profiling to detect and measure performance issues — including trusted preinstalled async-profiler v4.x setup, problem-driven…
001 Commands Inventory
jabrena/plinth
A skill your agent uses when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the…
Related
Categories
Questions about 051 Design Two Steps Methods
What does 051 Design Two Steps Methods do?
A skill your agent uses when a complex or risky code change should be split into Kent Beck's two-step method by first making the change easy through behavior-preserving preparatory refactoring, then…. 051 Design Two Steps Methods is an agent skill from jabrena/plinth. Use when a complex or risky code change should be split into Kent Beck's two-step method by first making the change easy through behavior-preserving preparatory refactoring, then making the intended behavior change once the design supports it.
When should I use 051 Design Two Steps Methods?
051 Design Two Steps Methods fits situations like: then making the intended behavior change once the design supports it; requests such as Apply two-step change; make this risky change safer; refactor before changing behavior.
How do I install 051 Design Two Steps Methods in Claude Code?
Run `npx skills add jabrena/plinth --skill 051-design-two-steps-methods -a claude-code`. Or copy the skill folder (skills/051-design-two-steps-methods in jabrena/plinth) into .claude/skills/051-design-two-steps-methods in your project. Claude Code loads it when a task matches its description.
How do I install 051 Design Two Steps Methods in Codex?
Run `npx skills add jabrena/plinth --skill 051-design-two-steps-methods -a codex`. Or copy the skill folder (skills/051-design-two-steps-methods in jabrena/plinth) into .agents/skills/051-design-two-steps-methods in your project. Codex loads it when a task matches its description.
Can I use 051 Design Two Steps Methods in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jabrena/plinth --skill 051-design-two-steps-methods -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/051-design-two-steps-methods, .gemini/skills/051-design-two-steps-methods, .github/skills/051-design-two-steps-methods and .opencode/skills/051-design-two-steps-methods in your project.
What does 051 Design Two Steps Methods need to run?
SKILL.md names no scripts, command-line tools or credentials: 051 Design Two Steps Methods is instructions for the agent only.
Does 051 Design Two Steps Methods access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is 051 Design Two Steps Methods safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does 051 Design Two Steps Methods use?
051 Design Two Steps Methods is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does 051 Design Two Steps Methods use?
About 973 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.6k tokens, read only when the agent opens those files.
What are the alternatives to 051 Design Two Steps Methods?
Skills that share tags, products or a category with 051 Design Two Steps Methods: Guidelines (akash-network/node, 1.1k stars), Component Refactoring (langflow-ai/langflow, 155k stars), Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars) and ast-grep Structural Search (code-yeongyu/oh-my-openagent, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains 051 Design Two Steps Methods?
jabrena (a GitHub user) maintains it in jabrena/plinth, which has 447 GitHub stars. The repository holds 124 skills in this directory. The repository was last updated on October 7, 2026.
Source: jabrena/plinth on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.