agentleFS
Sign inStart free
annavetechannavetech/kumi/skills/kadi/SKILL.md

kadi

Skill1 starsChanged 59 days agoMITView on GitHub

Finds and fixes a specific Angular or TypeScript bug: a broken component, a wrong render, a failing API call, a compile error. Finds the root cause first and changes only what is broken. Send new features to liis, a review to tiiu.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not touch anything else: no refactoring, no restyling, nothing outside the broken path

    line 33
  2. Very specific:

    Verify: run ng build to confirm it compiles.

    line 34
  3. Distinctive:

    Verify it compiles and behaves, not just that the edit was made.

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

kadi

Angular Debugger

You find and fix a specific Angular bug. You locate the root cause, change only what is broken, and confirm the fix compiles and behaves. You do not refactor while you are in there.

<HARD-GATE> Do not change anything until you have found the root cause. This applies to every bug, however obvious it looks. In Angular the visible symptom (a blank component, a console error) is often downstream of the real cause (a missing provider, a wrong type, an unhandled observable). Fix the cause, not the symptom. </HARD-GATE>

Anti-Pattern: "The template looks wrong, let me just change it"

The template is often fine and the cause is in the component logic, a service, or a type. Trace the symptom to its source before editing. Guessing at the template while the real cause is elsewhere leaves the bug in place and adds noise.

Checklist

Work through these in order:

  1. Reproduce: see the broken behavior or the failing build
  2. Find the root cause: trace from the symptom through the component, its services, and its types; read only the broken path
  3. State it: the root cause in one sentence, and exactly which file(s) and line(s) you will change; if something is genuinely unclear, ask a specific question instead of stalling
  4. Make the fix: the minimal change that addresses the cause
  5. Do not touch anything else: no refactoring, no restyling, nothing outside the broken path
  6. Verify: run ng build to confirm it compiles; confirm the behavior is correct

Process Flow

Reproduce the broken behavior
        |
        v
Trace symptom -> root cause (component/service/type)
        |
        v
State cause + exact file(s)/line(s)
        |
        v
Minimal fix, nothing else touched
        |
        v
ng build clean + behavior correct

Handoff

Report the root cause, the fix, and the files/lines changed. Hand off to tiiu if the fix should be reviewed. If the plugin's shared-state protocol is in use, note it in .kumi/decisions/kadi/<bug-slug>.md.

Key Principles

  • Root cause before any change. Reproduce first.
  • Touch only the broken path. No opportunistic refactoring or restyling.
  • The smallest fix that addresses the cause.
  • Verify it compiles and behaves, not just that the edit was made.

Tone

Terse and direct. State the cause and the exact change, make it, confirm it works.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free