Evidence-Backed Documentation Writer
bgauryy/octocode
Writes, repairs and copyedits project docs against the Google developer documentation style guide, verifying claims in the repository before stating them.
Use this when the user wants something designed — a screen, page, flow, app, or redesign — or says 'design', 'design brief', 'UI for'.
Install Design Brief
$ npx skills add dcodesdev/LetterSpace --skill design-brief -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dcodesdev/LetterSpace design-brief --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/dcodesdev/LetterSpace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/design-brief .claude/skills/design-brief && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "design-brief" agent skill from https://github.com/dcodesdev/LetterSpace/tree/main/.claude/skills/design-brief into .claude/skills/design-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-brief", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/dcodesdev/LetterSpace/tree/main/.claude/skills/design-briefType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add dcodesdev/LetterSpace --skill design-brief -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dcodesdev/LetterSpace design-brief --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dcodesdev/LetterSpace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/design-brief .agents/skills/design-brief && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "design-brief" agent skill from https://github.com/dcodesdev/LetterSpace/tree/main/.claude/skills/design-brief into .agents/skills/design-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-brief", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dcodesdev/LetterSpace --skill design-brief -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dcodesdev/LetterSpace design-brief --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dcodesdev/LetterSpace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/design-brief .cursor/skills/design-brief && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "design-brief" agent skill from https://github.com/dcodesdev/LetterSpace/tree/main/.claude/skills/design-brief into .cursor/skills/design-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-brief", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/dcodesdev/LetterSpace.git --path .claude/skills/design-brief--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add dcodesdev/LetterSpace --skill design-brief -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dcodesdev/LetterSpace design-brief --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dcodesdev/LetterSpace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/design-brief .gemini/skills/design-brief && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "design-brief" agent skill from https://github.com/dcodesdev/LetterSpace/tree/main/.claude/skills/design-brief into .gemini/skills/design-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-brief", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install dcodesdev/LetterSpace design-briefInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add dcodesdev/LetterSpace --skill design-brief -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dcodesdev/LetterSpace.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/design-brief .github/skills/design-brief && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "design-brief" agent skill from https://github.com/dcodesdev/LetterSpace/tree/main/.claude/skills/design-brief into .github/skills/design-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-brief", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dcodesdev/LetterSpace --skill design-brief -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dcodesdev/LetterSpace design-brief --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dcodesdev/LetterSpace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/design-brief .opencode/skills/design-brief && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "design-brief" agent skill from https://github.com/dcodesdev/LetterSpace/tree/main/.claude/skills/design-brief into .opencode/skills/design-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-brief", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
design-brief- GitHub stars
- 100
- Token cost
- ~1.4k tokens
- SKILL.md length
- 630 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
Use this when the user wants something designed — a screen, page, flow, app, or redesign — or says 'design', 'design brief', 'UI for'.
- Works in 6 steps: Understand the ask. Restate in one… → Ask what changes the answer. Who uses… → Ground it if there is a codebase. Read… → …
- Wants something designed — a screen
- SKILL.md covers The one rule, Never appears in the brief, Allowed, and wanted and How to work, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Design Brief is an agent skill from dcodesdev/LetterSpace. Use this when the user wants something designed — a screen, page, flow, app, or redesign — or says 'design', 'design brief', 'UI for'. Writes a requirements-only prompt to hand to a separate AI designer. Expresses needs, never design decisions: no layouts, components, styles, or libraries.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Architecture decision records. The repository describes itself as: Self-hosted open source newsletter platform for managing subscribers and sending campaigns. The licence is MIT.
When your agent uses it
- Wants something designed — a screen
- Tasks that involve Architecture decision records
Example prompts
- “design”
- “design brief”
- “UI for”
- “/design-brief”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Understand the ask. Restate in one sentence what is being designed and for whom.
- Ask what changes the answer. Who uses it, what they are trying to accomplish, what data exists, what must never happen, what already…
- Ground it if there is a codebase. Read what exists to learn the real entities, fields, states, and rules. Report them as facts about the…
- Write the brief in the shape below.
- Check every line against the one rule, then delete any line that fails. Re-read the "never appears" list and scan for those words.
- Hand it over — output the brief in a single fenced block the user can copy straight to the designer. Say nothing about how it should look.
What it can do on your machine
Read from SKILL.md and the folder at commit a06ec86. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Design Brief loads about 1.4k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 630 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from dcodesdev/LetterSpace at commit a06ec86, republished under its MIT licence (© dcodesdev). 630 words, ~1,390 tokens.
Download SKILL.mdSave it as
.claude/skills/design-brief/SKILL.md (or your agent's skills folder).- name
- design-brief
- description
- Use this when the user wants something designed — a screen, page, flow, app, or redesign — or says 'design', 'design brief', 'UI for'. Writes a requirements-only prompt to hand to a separate AI designer. Expresses needs, never design decisions: no layouts, components, styles, or libraries.
Design brief
You are not the designer. You write the brief that a separate AI designer works from, and the designer makes every design decision.
Your only job: turn what the user wants into a clear statement of what someone must be able to do, see, and know. Then hand it over.
The one rule
Describe the need, never the solution.
Every line of the brief must survive this test: could two good designers read this and arrive at completely different-looking screens that both satisfy it? If no, you have smuggled in a design decision — cut it.
| Wrong (a decision) | Right (a need) |
|---|---|
| A table listing the user's projects | The user can see all their projects and tell them apart at a glance |
| A modal to confirm deletion | The user must confirm before a project is deleted |
| A sidebar with navigation | The user can move between projects, settings, and billing from anywhere |
| A green badge for active status | The user can tell an active project from an archived one |
| Use a card grid, three columns | The user compares projects side by side |
| A search bar at the top | The user can find one project among hundreds |
| Collapse the form into steps | The user can complete signup without being overwhelmed by it at once |
| A dashboard with stat tiles | On arriving, the user sees how their work is doing without digging |
Never appears in the brief
- Component or element names: table, modal, card, sidebar, drawer, dropdown, tab, accordion, toast, badge, button, form, grid, carousel, tooltip, stepper, breadcrumb.
- Layout: columns, rows, above/below, left/right, header, footer, sticky, position, width, spacing, responsive breakpoints.
- Visual style: colors, fonts, sizes, weights, borders, shadows, radius, icons, imagery, animation, dark mode, "modern", "clean", "minimal", "sleek".
- Technology: any framework, library, design system, CSS, HTML, code, file names, or snippets.
- Comparisons that import a design: "like Linear", "Stripe-style", "Notion-ish".
If the user themself asks for one of these, keep it — record it under Constraints as their requirement, worded as theirs. Never add your own.
Show full SKILL.md (296 more words)Show less
Allowed, and wanted
- Who the person is and what they came to do.
- What they must be able to do, see, find, compare, understand, decide.
- What information must be available, and which pieces matter most to them.
- What must be true before an action happens (confirmation, permission, payment).
- What happens when things go wrong, are empty, are loading, are too many, or are too long.
- Hard constraints from the real world: offline use, one-handed on a phone, screen reader, a legally required disclosure, a locked-in flow.
- How you know the design worked.
How to work
- Understand the ask. Restate in one sentence what is being designed and for whom.
- Ask what changes the answer. Who uses it, what they are trying to accomplish, what data exists, what must never happen, what already exists around it. Ask only the questions whose answers would change the brief; assume sensible defaults for the rest and say which you assumed.
- Ground it if there is a codebase. Read what exists to learn the real entities, fields, states, and rules. Report them as facts about the domain, not as UI.
- Write the brief in the shape below.
- Check every line against the one rule, then delete any line that fails. Re-read the "never appears" list and scan for those words.
- Hand it over — output the brief in a single fenced block the user can copy straight to the designer. Say nothing about how it should look.
Shape of the brief
# <What is being designed>
## Purpose
One or two sentences: what this is for, and what it changes for the person using it.
## Who it is for
Who they are, what they already know, the situation they are in when they use it.
## What they need to be able to do
- The user can ...
- The user can ...
Ordered by how central it is. Most important first.
## What they need to see
- The user sees ...
Say why each piece matters to them, not where it goes.
## Rules and conditions
What must be true, what is not allowed, what needs confirming, who may do what.
## Situations to cover
Empty, first time, loading, failure, no permission, far too much data, far too
little, extreme values, interrupted midway.
## Constraints
Real-world limits, and anything the user explicitly insisted on (marked as theirs).
## Done when
How to tell the design succeeded — in terms of what the person can now do.
## Open questions
What is still unknown, and what was assumed in the meantime.Drop any section with nothing real to say. An empty heading is noise.
Keep it
- Plain. Every requirement is a sentence a non-designer would say out loud.
- Specific about the need, silent about the answer.
- Honest about gaps: an open question beats an invented requirement.
© dcodesdev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/design-brief of dcodesdev/LetterSpace.
Open the folder on GitHubat commit a06ec86
Compare with similar skills
Design Brief next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Design Brief this skilldcodesdev/LetterSpace | 100 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Evidence-Backed Documentation Writerbgauryy/octocode | 946 | — | ~2k | Automated safety check: Pass | MIT | |
| Agent Stylepchalasani/claude-code-tools | 2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Diataxis Docspmndrs/glyph | 392 | — | ~1.4k | Automated safety check: Pass | MIT | |
| RFC Creatortech-leads-club/agent-skills | 7k | — | ~2.9k | Automated safety check: Pass | CC-BY-4.0 | |
| Expectationscitypaul/.dotfiles | 739 | — | ~1.2k | Automated safety check: Pass | Custom licence |
Similar skills
Agent Style
pchalasani/claude-code-tools
Literature-backed English technical-prose writing rules (agent-style, 21 rules).
Diataxis Docs
pmndrs/glyph
Design, classify, write, audit, or restructure technical documentation with the Diátaxis framework.
RFC Creator
tech-leads-club/agent-skills
Drafts Request for Comments documents that lay out a proposal, the options weighed and the decision needed, so approvers can align before a major change.
Expectations
citypaul/.dotfiles
Decide where a learning, gotcha, or decision should live so it is not lost, and capture it there while context is fresh.
Codd Fable Consult
yohey-w/codd-dev
Consult Claude Fable 5 (Anthropic's most capable model for deep, long-horizon reasoning — or whichever model currently holds that role) for a genuinely hard, novel CoDD architectural design…
More from dcodesdev/LetterSpace
New Plan
dcodesdev/LetterSpace
Use this when the user wants to create a new plan, start a new feature, begin a new project, or says 'new plan'.
Refactor
dcodesdev/LetterSpace
Use this when the user wants to refactor the codebase, clean up code, reduce duplication, or says 'refactor' / 'new refactor'.
Document
dcodesdev/LetterSpace
Use this when writing or updating documentation — a README, docs/ page, CLAUDE.md, changelog entry, or doc comments — or when the user says 'document this'.
Brainstorm
dcodesdev/LetterSpace
Use this when the user wants to brainstorm, think through an idea, explore approaches, weigh options, or says 'brainstorm' / 'let's think about'.
Related
Categories
Questions about Design Brief
What does Design Brief do?
Use this when the user wants something designed — a screen, page, flow, app, or redesign — or says 'design', 'design brief', 'UI for'. Design Brief is an agent skill from dcodesdev/LetterSpace. Use this when the user wants something designed — a screen, page, flow, app, or redesign — or says 'design', 'design brief', 'UI for'.
When should I use Design Brief?
Design Brief fits situations like: wants something designed — a screen; tasks that involve Architecture decision records.
How do I install Design Brief in Claude Code?
Run `npx skills add dcodesdev/LetterSpace --skill design-brief -a claude-code`. Or copy the skill folder (.claude/skills/design-brief in dcodesdev/LetterSpace) into .claude/skills/design-brief in your project. Claude Code loads it when a task matches its description.
How do I install Design Brief in Codex?
Run `npx skills add dcodesdev/LetterSpace --skill design-brief -a codex`. Or copy the skill folder (.claude/skills/design-brief in dcodesdev/LetterSpace) into .agents/skills/design-brief in your project. Codex loads it when a task matches its description.
Can I use Design Brief in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dcodesdev/LetterSpace --skill design-brief -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/design-brief, .gemini/skills/design-brief, .github/skills/design-brief and .opencode/skills/design-brief in your project.
What does Design Brief need to run?
SKILL.md names no scripts, command-line tools or credentials: Design Brief is instructions for the agent only.
Does Design Brief access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Design Brief safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Design Brief use?
Design Brief is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Design Brief use?
About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Design Brief?
Skills that share tags, products or a category with Design Brief: Evidence-Backed Documentation Writer (bgauryy/octocode, 946 stars), Agent Style (pchalasani/claude-code-tools, 2k stars), Diataxis Docs (pmndrs/glyph, 392 stars) and RFC Creator (tech-leads-club/agent-skills, 7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Design Brief?
dcodesdev (a GitHub user) maintains it in dcodesdev/LetterSpace, which has 100 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 2, 2026.
Source: dcodesdev/LetterSpace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.