agentleFS
Sign inStart free
e-dule-dul/opencl-lab/.claude/skills/design-creation/SKILL.md

design-creation

Skill0 starsChanged 8 months agoMITView on GitHub

Standard operating procedure for creating Applied OpenCL Lab design documents. Use this skill whenever a new module design or architecture document is requested.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 2 are distinctive, and 5 are 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.

  • 5

    Very specific

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

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

    Read existing: Read design workflow/design/design_[module_name].md if it's available.

    line 11
  2. Very specific:

    Gather Context: Read workflow/design/00-executive-summary.md and rules/00_master_specs.md to understand the project philosophy and the …

    line 12
  3. Very specific:

    Fetch Template: Read the workflow/templates/design_doc_template.md file from the workspace to get the exact markdown structure required.

    line 13
  4. Very specific:

    NEVER include low-level execution logs, .cpp implementation details, or task definitions.

    line 16
  5. Distinctive:

    Keep the high-level status purely to Phases/Milestones (checkboxes).

    line 17
  6. Distinctive:

    Ensure performance gates are clearly defined based on the Executive Summary.

    line 18
  7. Very specific:

    Save: Write the final output to workflow/design/design_[module_name].md.

    line 19

≈ “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

Design Document Creation Skill

You are executing the Strategy phase of the Applied OpenCL Lab workflow.

Instructions

  1. Read existing: Read design workflow/design/design_[module_name].md if it's available.
  2. Gather Context: Read workflow/design/00-executive-summary.md and rules/00_master_specs.md to understand the project philosophy and the specific module's goals.
  3. Fetch Template: Read the workflow/templates/design_doc_template.md file from the workspace to get the exact markdown structure required.
  4. Draft the Design: Fill out the template for the requested module.
  5. Enforce Rules:
    • NEVER include low-level execution logs, .cpp implementation details, or task definitions.
    • Keep the high-level status purely to Phases/Milestones (checkboxes).
    • Ensure performance gates are clearly defined based on the Executive Summary.
  6. Save: Write the final output to workflow/design/design_[module_name].md.

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