// Use this skill when faced with a difficult debugging task where you need to replicate some bug or behavior in order to see what is going wrong.
IMMEDIATELY USE THIS SKILL when creating or develop anything and before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation
Use when implementing user interfaces or user experiences - guides through exploration of design variations, frontend setup, iteration, and proper integration
Use when you need to create a new custom skill for a profile - guides through gathering requirements, creating directory structure, writing SKILL.md, and optionally adding bundled scripts
Use this when you have completed some feature implementation and have written passing tests, and you are ready to create a PR.
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
ALWAYS load this skill if it is not already loaded, for ANY user query or conversation - establishes the Nori workflow, protected-branch check, operating mode, tone, and coding guidelines before any other work
| name | creating-debug-tests-and-iterating |
| description | Use this skill when faced with a difficult debugging task where you need to replicate some bug or behavior in order to see what is going wrong. |
From this point on, ignore any existing tests until you have a working example validated through a new test file.
To test different kinds of applications, write scripts that test the application interfaces. Your testing should be as close to 'real' as possible.
Identify the application boundary to be tested and the tools you need to test it.
CLI Tool:
./path/to/cli.sh arg1 arg2
subprocess.run(["./path/to/cli.sh", "arg1", "arg2"])
exec('./path/to/cli.sh', (error, stdout, stderr) => {
if (error) {
console.error(`exec error: ${error}`);
return;
}
console.log(`stdout: ${stdout}`);
console.error(`stderr: ${stderr}`);
});
API:
Start the server:
cd backend && python server.py&
cd frontend && npm run dev&
Call to the server using scripting language of choice.
Do NOT get in a loop where you just keep running other tests. In this mode, you should ignore other tests entirely until it works.
Web servers or web apps: use playwright (read the .claude/skills/webapp-testing/SKILL.md) TUI tools: use tmux with screen capture CLI tools: use bash