agentleFS
flllflll/grow-your-own-skills/skills/core/SKILL.md

core

Skill0 starsChanged 5 months agoCC0-1.0View on GitHub

Required reading. Read this first at the start of every session, before anything else. It holds the minimal rules that apply to all work, plus the routing table that says which other skills to read. Other skills are read only when the routing table or their own description says so.

29 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ts-core, native-ui and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • VercelSkill

    ts-core

    Authoring guide for the primary Native SDK app-logic path: TypeScript app cores - Model, Msg, update, and the pure functions they call, written in the closed app-core subset, checked by the @native-sdk/core frontend, and compiled ahead-of-time to native code by the external core compiler. Use for new apps unless the user explicitly chose Zig, when writing or modifying a src/core.ts app core, fixing subset checker errors (NS1001-NS1069), or deciding how to express state, messages, text (bytes and the byte-text string methods), text input, continuous controls (sliders, scroll), effects (Cmd), subscriptions (Sub), the host-event wiring channels (frameMsg, keyMsg, pinchMsg, dropMsg, appearanceMsg, chromeMsg, envMsgs, app manifest assets), derived values, the view_unbound lint opt-out, local mutation of owned arrays, or how to split a core into modules under src/ (relative imports, namespace imports, @native-sdk/core/text, @native-sdk/core/events). Use ts-services alongside this guide for src/services work.

    Also in 3 projects that use this

  • VercelSkill

    native-ui

    Authoring guide for the Native markup (.native) view tier of native-rendered Native SDK apps. TypeScript cores are the default and use this skill together with ts-core; Zig cores are an explicit alternative and this guide labels their lower-level UiApp recipes. Use when building or modifying native UI (widgets, layout, bindings, messages), writing .native files, wiring views to Model/Msg/update, testing markup views, or verifying a native app through the automation harness.

    Also in 3 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 3 projects that use this

  • +3 more from vercel-labs

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When it grows past that, move the overflow into a new skill and add one row to the routing table below.

    line 13
  2. Distinctive:

    When reporting work as done, include the commands you ran and their real output.

    line 18
  3. Distinctive:

    Before any task that touches multiple files or deletes anything: restate the request in 3 lines, confirm the goal / definition of done / …

    line 20
  4. Very specific:

    When the user corrects you about the same thing for the second time, read skill-coach and propose turning the correction into a skill.

    line 23
  5. Very specific:

    If a request matches a row below, read that skill's SKILL.md before starting the work.

    line 29

“Common” is measured: kept by at least 6 in 10 of the 20 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

core — the minimal rules for every session

<!-- Fill in every <...> with your own words. Keep this file at 5-10 rules. When it grows past that, move the overflow into a new skill and add one row to the routing table below. -->
  1. Respond in <your language>. (Example: respond in English, commit messages in English too.)
  2. When reporting work as done, include the commands you ran and their real output. Never say "this should work" without having run it.
  3. Before any task that touches multiple files or deletes anything: restate the request in 3 lines, confirm the goal / definition of done / allowed scope, and get agreement before writing.
  4. When the user corrects you about the same thing for the second time, read skill-coach and propose turning the correction into a skill.
  5. <your project-specific rule> (Example: never push directly to main.)

Routing table

If a request matches a row below, read that skill's SKILL.md before starting the work. Every new skill gets one row here.

When the request involves...Read
a repeated correction, or creating/improving/pruning a skillskill-coach
(example: commit / PR / branching)(example: git-rules)

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.