wheslleyrimarwheslleyrimar/BuildCLI-Agents/.claude/skills/interface/SKILL.md

interface

Skill3 starsChanged 11 days agoMITView on GitHub

Client-side work — components, pages, state, routing, and API wiring. Reads only [band:interface] from .buildcli/context.md.

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Do not open .buildcli/context.md directly — with the harness enforced, that read is blocked
line 35
Distinctive:
Do not open service logic, migrations, or the delivery band unless the task explicitly reaches into them.
line 38
Very specific:
Run .buildcli/runtime/bcx band interface to load the band.
line 47
Distinctive:
Check the API contract against what the server actually exposes.
line 51
Distinctive:
Do not touch service or migration files in this task.
line 62
Very specific:
Follow the component and styling conventions recorded in [band:interface].
line 63

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Skill: interface

Metadata

Agent: Claude
Version: 0.1.0
Band: [band:interface] in .buildcli/context.md

Purpose

Own what the user sees and touches: components, views, client state, routing, styling, and the layer that talks to the API. Reads a single band to keep the context cost flat.

When to use

Building or changing a component or page
Managing client-side state or routing
Connecting the UI to a backend endpoint
Applying the design system or styling conventions
Fixing an accessibility or internationalization defect

Context loading (minimal)

Read only:

The [band:interface] block, via the runtime:
```
.buildcli/runtime/bcx band interface
```
Do not open .buildcli/context.md directly — with the harness enforced, that read is blocked
The specific component(s) or page(s) named by the task

Do not open service logic, migrations, or the delivery band unless the task explicitly reaches into them.

Inputs

A task description, or the component/page path(s) to change
Optional: the related brief.md from the active blueprint

Workflow

Run .buildcli/runtime/bcx band interface to load the band. Nothing else from the context file.
Locate the component, page, or state slice the task points at.
Open only the source files that matter to it.
Make the smallest change that satisfies the task and matches the framework and design-system conventions.
Check the API contract against what the server actually exposes. A mismatch is a flag, not a fix — the server is another band.
Report back: what changed, why, and what still needs attention.

Output

The code change, with a short explanation
The list of files touched
Flags for downstream impact: API contract, state shape, tests

Constraints

Do not touch service or migration files in this task. Flag them instead.
Follow the component and styling conventions recorded in [band:interface].
One component concern per task. Never fold a broad refactor into a feature change.

Download now (ZIP)

Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
kecoma1/MQL5-SKILLS★ 17same name
calebnewtonusc/Chewbacca★ 8same name
jeremy-farnault/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- auditSkill
- briefSkill
- buildSkill
- deliverySkill
- design-reviewSkill
- focusSkill
- forgeSkill
- patchSkill
- pulseSkill
- rigSkill
- serviceSkill
- shapeSkill
- storeSkill
- surveySkill
- verifySkill
- worklistSkill

Does it work?

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

Reviews can't be read right now.

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