agentleFS
nteractnteract/desktop/.agents/skills/architecture/SKILL.md

architecture

Skill183 starsChanged 18 days agoBSD-3-ClauseView on GitHub

Architecture and documentation framing for cross-cutting repo decisions, docs taxonomy placement, ADRs, memos, PRDs, implementation plans, audits, measurements, runbooks, and source-grounded proposals. Use when deciding where durable docs belong, drafting or moving architecture/product/design docs, or promoting `.context/` notes into repo docs. Do not use for routine code changes unless they require durable cross-functional documentation.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 111 edited versions we read keep these.

  • 4

    Distinctive

    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
  1. Distinctive:

    Use this skill when the work is about durable architecture, product, or design documentation, or when deciding where a document belongs.

    line 8
  2. Very specific:

    Start working notes in .context/.

    line 14
  3. Distinctive:

    Keep routine implementation notes in the PR body, code comments, or final response.

    line 15
  4. Very specific:

    Read docs/README.md before creating or moving durable docs.

    line 33
  5. Distinctive:

    When moving docs, update indexes and cross-links.

    line 34
  6. Distinctive:

    Prefer the smallest durable artifact.

    line 36
  7. Very specific:

    Run focused link/path checks for moved docs and cargo xtask lint --fix before commit.

    line 38

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

Architecture and Documentation

Use this skill when the work is about durable architecture, product, or design documentation, or when deciding where a document belongs. Do not load it for routine implementation notes, test plans, or ordinary code changes.

Default Path

  • Start working notes in .context/.
  • Keep routine implementation notes in the PR body, code comments, or final response.
  • Promote only when the artifact should outlive the immediate change and help product, design, engineering, research, or AI collaborators.

Placement

  • docs/memos/: shared thinking, research, options, and RFC-style proposals before there is a decision.
  • docs/adr/: durable technical decisions, invariants, compatibility boundaries, and rejected alternatives.
  • docs/prd/: user-facing requirements, workflows, roles, and launch criteria.
  • docs/plans/: scoped execution plans for already-framed work.
  • docs/audits/: source-backed evidence and follow-up lists.
  • docs/measurements/: benchmark evidence and performance models.
  • docs/runbooks/: operational procedures.

Workflow

  1. Read docs/README.md before creating or moving durable docs.
  2. When moving docs, update indexes and cross-links; search for old paths with git grep.
  3. Prefer the smallest durable artifact. Mark contentious sections as open questions or commentary instead of forcing them into a decision.
  4. Run focused link/path checks for moved docs and cargo xtask lint --fix before commit.

Download now (ZIP)

  • Other versions127 projects use a version of this.

    Word for word · 1

    1. nteract/nteract★ 183100% same

    Edited · 0

    None found.

    Wrote their own version · 126

    1. anthropics/knowledge-work-plugins★ 34ksame name
    2. iOfficeAI/AionUi★ 34ksame name
    3. vudovn/ag-kit★ 8.2ksame name
    4. vudovn/antigravity-kit★ 8.2ksame name
    5. nativewind/nativewind★ 8.1ksame name
    6. PaulWoitaschek/Voice★ 3.2ksame name
    7. wellwelwel/poku★ 1.2ksame name
    8. Alwurts/simple-ai★ 755same name
    9. patrickjaja/claude-desktop-extra★ 713same name
    10. ktnyt/cclsp★ 673same name

    116 more not listed

    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.

  • Used alongsideProjects with it also use intelligent-routing, bash-linux and 10 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.
    • SKB3002Skill

      intelligent-routing

      Automatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions.

      Also in 6 projects that use this

    • xenitV1Skill

      bash-linux

      Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.

      Also in 8 projects that use this

    • xenitV1Skill

      red-team-tactics

      Red team tactics principles based on MITRE ATT&CK. Attack phases, detection evasion, reporting.

      Also in 8 projects that use this

    • xfstudioSkill

      rust-pro

      Master Rust 1.75+ with modern async patterns, advanced type system

      Also in 6 projects that use this

    • +8 more from xenitV1
  • In this repository9 other files it gives its agents.

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.