design-process

design-process is a skill for Claude Code, Codex from flitzrrr/frontend-design-skills. It costs 34 tokens per session (1,439 once invoked), scanned A, original, MIT.

A structured process for taking a design from a brief through concepts, wireframes, prototypes and visual design to review and handoff. A wireframe is a simple layout sketch, while a prototype is an interactive design model.

In plain words
What is it for?
Use it to organise design projects, complete briefs, explore concepts, create prototypes, run reviews and prepare work for developers.
Why use it?
It turns unclear requirements into decisions that can be reviewed and tested before development is finished.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to organise design projects, complete briefs, explore concepts, create prototypes, run reviews and prepare work for developers.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/flitzrrr/frontend-design-skills/design-process
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add flitzrrr/frontend-design-skills --skill design-process
Clone the repo
git clone --depth 1 https://github.com/flitzrrr/frontend-design-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for design-process

README.md
[![agentmods](https://agentmods.dev/badge/skills/flitzrrr/frontend-design-skills/design-process/github.svg)](https://agentmods.dev/skills/flitzrrr/frontend-design-skills/design-process)
Your own site
<a href="https://agentmods.dev/skills/flitzrrr/frontend-design-skills/design-process"><img src="https://agentmods.dev/badge/skills/flitzrrr/frontend-design-skills/design-process/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for design-process

Your own site · 80×15
<a href="https://agentmods.dev/skills/flitzrrr/frontend-design-skills/design-process"><img src="https://agentmods.dev/badge/skills/flitzrrr/frontend-design-skills/design-process.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,439 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00034 $0.01439
Opus 5 $0.00017 $0.00720
Sonnet 5 $0.00007 $0.00288
Haiku 4.5 $0.00003 $0.00144

Measured 9d ago against content hash 69cd638cfdc9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

design-process scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills-src/design-process/SKILL.md · 149 lines

How it starts

The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Design Process

Projects rarely fail in execution. They fail due to unclear or incomplete briefings. Structure creates space for creativity.

Scope

Use this skill when you:

  • Structure a design project from the beginning
  • Capture, validate, or complete a briefing
  • Create wireframes or prototypes
  • Use moodboards as a decision-making tool
  • Prepare the handoff to development
  • Plan a design review or usability test

Principles

1. Structure Creates Space for Creativity

A systematic process prevents creative energy from dissipating into disorientation.

2. The Briefing Is Half the Battle

Unclear briefings are the most common cause of failed projects.

3. Diverge, Then Converge

Every phase has an exploratory part (opening options) and an evaluative part (assessing and narrowing options).

4. User-Centricity Is Non-Negotiable

Design that only pleases the client but ignores the user has failed.

5. Differentiation Before Convention

Good design requires the courage to deliberately break conventions where it serves the user.

6. Iteration Over Perfection

Better to show early and gather feedback than to polish in isolation for too long.

7. Documentation Is Not an Afterthought

Design decisions that are not documented get lost during implementation.

Rules

DO: Capture and Validate the Briefing Systematically

A complete briefing contains:

  • Current State: What already exists? Why is it no longer sufficient?
  • Goals: What should the design specifically achieve? (formulated as measurable outcomes)
  • Target Audience: Who are the users? (reference to Customer Journey)
  • Constraints: Budget, timeline, technical requirements, corporate design guidelines.
  • Competition: What are competitors doing? What should deliberately differ?
  • Success Criteria: How will success be measured?

Review every briefing for contradictions, gaps, and implicit assumptions.

DO: Follow the 7 Steps of the Design Process

  1. Briefing and Research — Clarify requirements, gather data, analyze competition.
  2. Strategy and Concept — Positioning, information architecture, content strategy.
  3. Wireframing — Structural layouts without visual design. Focus on hierarchy and user flow.
  4. Visual Design — Colors, typography, imagery, design grid.
  5. Prototyping — Interactive prototypes for real user flows.
  6. Review and Testing — Usability tests, accessibility checks, stakeholder feedback.
  7. Handoff and Documentation — Structured delivery with style guide and specifications.

Read the full file on GitHub · 149 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 149 lines · 34 tokens per session scan A 69cd638cfdc9

Subscribe to this mod's changes

design-process is a skill published in the GitHub repository flitzrrr/frontend-design-skills (5 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 1,439 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

webgl-holographic-foil

A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.

nexu-io/open-design · 41 tokens

html-ppt-hermes-cyber-terminal

OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.

nexu-io/open-design · 53 tokens

html-ppt-taste-brutalist

16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).

nexu-io/open-design · 78 tokens

visual-ralph

Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.

Yeachan-Heo/oh-my-codex · 50 tokens

accessibility

Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.

microsoft/hve-core · 47 tokens

make-resume

A Chinese-language tool for creating editable HTML resumes that can be changed in a browser and printed to PDF. It uses available resume templates when they are installed and otherwise provides a simpler fallback.

Hisn00w/ASu-skills · 86 tokens