agentleFS
Sign inStart free
adityareddy-devadityareddy-dev/deskstudio/skills/help/SKILL.md

help

Skill43 starsChanged 23 days agoMITView on GitHub

What Desk Studio is and how to use it. The commands, the desks, the loop, the tiers, where files go.

76 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-stories, story-done 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.
  • lilangMaxSkill

    create-stories

    Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.

    Also in 9 projects that use this

  • lilangMaxSkill

    story-done

    End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.

    Also in 9 projects that use this

  • +10 more from lilangMax

The file

Create a free account to mount
Files
SKILL.md

Tell the user, in plain words and under 25 lines:

  • Desk Studio is a design studio inside this coding agent. You ask for a thing, the Design Manager staffs desks, three roughs are made, the Art Director picks one and writes notes, a builder polishes, proof checks the pixels, the Creative Director scores it against an eight-axis rubric, and it comes back when it clears the bar.
  • Commands in this build: /desk:init (set up the brand and models), /desk:design <ask> (anything), /desk:help.
  • Desks in this build: Creative Director, Art Director, UI Designer. The full studio has 42.
  • Tiers: director (opus), senior (sonnet), builder (haiku) by default. Change them in .desk/project.json or with --quality best|thrifty|studio.
  • Where things go: .desk/DESIGN.md is the brand, .desk/out/<job>/ the files, .desk/jobs/<job>/ the renders, state and scores.
  • Nothing leaves the machine except the model calls the agent already makes.

Then show one example: /desk:design a LinkedIn card announcing our v2 launch.

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