agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/nvcf/src/uis/nvcf-ui/.agents/skills/add-feature/SKILL.md

add-feature

Skill268 starsChanged 3 days agoApache-2.0View on GitHub

Add new functionality to the nvcf-ui app: a new page, a new domain feature folder, or an extension of an existing feature. Covers deciding where code goes, scaffolding, wiring a route, tests, mocks, and the completion checklist. Use when building a new screen, view, or page, adding a feature folder, or deciding whether to extend an existing feature, even if the user does not say "feature".

27 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 3 are distinctive, and 7 are very specific to this project.

  • 0

    Common

    Most of the 25 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 7

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read ARCHITECTURE.md first.

    line 15
  2. Distinctive:

    Check for an existing component or hook before writing a new one.

    line 27
  3. Very specific:

    If an endpoint has no generated hook, update the spec and regenerate.

    line 28
  4. Distinctive:

    Put each piece where it belongs:

    line 30
  5. Distinctive:

    Do not import one feature from another.

    line 37
  6. Very specific:

    Add the route with the routing skill.

    line 38
  7. Very specific:

    Add tests with the testing skill.

    line 41
  8. Very specific:

    Add MSW scenarios for key states (empty, error, a status that changes the view) in ui/src/mocks/scenarios/<feature>/.

    line 42
  9. Very specific:

    Import anything outside the current folder with ~/, including within a feature.

    line 44
  10. Very specific:

    Run task lint:fix to apply formatting and license headers.

    line 55

“Common” is measured: kept by at least 6 in 10 of the 25 edited versions of this file we could read. “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

Adding a feature

Read ARCHITECTURE.md first. It defines the layers this procedure follows: pages in ui/src/routes/, domain code in ui/src/features/, shared code in ui/src/components/, ui/src/hooks/, ui/src/lib/, and ui/src/utils/.

Steps

  1. Decide what you are adding.
    • A new domain (new data, concepts, or API surface): create ui/src/features/<domain>/.
    • More of an existing domain: extend that feature folder.
    • A new page: add a route file. A page is not a feature; it composes features.
  2. Check for an existing component or hook before writing a new one.
  3. If an endpoint has no generated hook, update the spec and regenerate. Use the codegen skill.
  4. Put each piece where it belongs:
    • Domain building blocks (cards, badges, panels, domain hooks, constants, types) go in the feature: components/, hooks/, types/, and constants.ts, created only when needed.
    • Page scaffolding (heading, layout, composition, table columns, URL-state wiring) goes in the route file.
    • Domain-agnostic code needed by several features graduates to shared code.
  5. Do not import one feature from another. Compose features in the route file.
  6. Add the route with the routing skill. Add a nav entry in ui/src/routes/__root.tsx for a new top-level page.
  7. For UI, use the kaizen-ui skill. Prefer KUI components over plain HTML.
  8. Add tests with the testing skill.
  9. Add MSW scenarios for key states (empty, error, a status that changes the view) in ui/src/mocks/scenarios/<feature>/. See the codegen skill.
  10. Import anything outside the current folder with ~/, including within a feature. ./ is fine for files in the same folder; never use ../.

Examples

  • Page: ui/src/routes/functions/index.tsx
  • Feature: ui/src/features/functions/
  • Page composing several features: ui/src/routes/index.tsx

Validate

  1. Run task lint:fix to apply formatting and license headers.
  2. Run task verify.
  3. Fix failures and rerun until clean.

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