web design engineer

Design Community

Skill notes

Scope

✅ Applicable: Visual front-end deliverables (pages / prototypes / slide decks / visualizations / animations / UI mockups / design systems) ❌ Not applicable: Back-end APIs, CLI tools, data-processing scripts, pure logic development with no visual requirements, performance tuning, and other terminal tasks

Step 0: Verify Facts Before Anything Else

Highest priority — runs before clarifying questions. When the request mentions a specific product, brand, technology, SDK, or event you're not 100% sure about, the first action is WebSearch to verify existence, release status, latest version, and key specs from authoritative sources. Never assert from training data. Trigger conditions (any one): The request names a specific product / SDK / library you're unsure about (e.g., a new device, a recently announced model)

Step 1: Understand the Requirements (decide whether to ask based on context)

Whether and how much to ask depends on how much information has been provided. Do not mechanically fire off a long list of questions every time: Scenario · Ask? "Make a deck" (no PRD, no audience) · ✅ Ask extensively: audience, duration, tone, variants "Use this PRD to make a 10-min deck for Eng All Hands" · ❌ Enough info — start building "Turn this screenshot into an interactive prototype" · ⚠️ Only ask if the intended interactions are unclear

Step 2: Gather Design Context (by priority)

Good design is rooted in existing context. Never start from thin air.

Step 3a: Position Four Questions Before Picking a System

Before listing color/typography/spacing tokens, articulate four positioning questions for each artifact (or each slide / screen / scene): Narrative role: Hero / transition / data / pull-quote / closing? (Each demands a different visual register.) Viewing distance: 10cm phone / 1m laptop / 10m projector? (Drives type scale and information density.) Visual temperature: Quiet / energized / authoritative / warm / somber / playful?

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Design
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@ConardLi · no license declared
Token usage
Heavy
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 0: Verify Facts Before Anything Else

Highest priority — runs before clarifying questions. When the request mentions a specific product, brand, technology, SDK, or event you're not 100% sure about, the first action is `WebSearch` to verify existence, release status, latest version, and key specs from authoritative sources. Never assert from training data. Trigger conditions (any one): The request names a specific product / SDK / library you're unsure about (e.g., a new device, a recently announced model)

02
Step 1: Understand the Requirements (decide whether to ask based on context)

Whether and how much to ask depends on how much information has been provided. Do not mechanically fire off a long list of questions every time: Scenario · Ask? "Make a deck" (no PRD, no audience) · ✅ Ask extensively: audience, duration, tone, variants "Use this PRD to make a 10-min deck for Eng All Hands" · ❌ Enough info — start building "Turn this screenshot into an interactive prototype" · ⚠️ Only ask if the intended interactions are unclear

03
Step 2: Gather Design Context (by priority)

Good design is rooted in existing context. Never start from thin air.

04
Step 3a: Position Four Questions Before Picking a System

Before listing color/typography/spacing tokens, articulate four positioning questions for each artifact (or each slide / screen / scene): Narrative role: Hero / transition / data / pull-quote / closing? (Each demands a different visual register.) Viewing distance: 10cm phone / 1m laptop / 10m projector? (Drives type scale and information density.) Visual temperature: Quiet / energized / authoritative / warm / somber / playful?

05
Step 3: Declare the Design System Before Writing Code

Before writing the first line of code, articulate the design system in Markdown and let the user confirm before proceeding: If you picked a recipe from `references/style-recipes/`, paste its concrete palette / typography / spacing / radius / shadow / motion values straight into the block above — that catalog exists so you don't have to invent these on the fly, which is the leading cause of AI-default Inter + #3b82f6 mush. Load only the one recipe file you're using, not the whole catalog.

06
Step 4: Show a v0 Draft Early

Don't hold back a big reveal. Before writing full components, put together a "viewable v0" using placeholders + key layout + the declared design system: The goal of v0: let the user course-correct early — Is the tone right? Is the layout direction right? Are the variant directions right? Includes: core structure + color/typography tokens + key module placeholders (with explicit markers like `[image]` `[icon]`) + your list of design assumptions

07
Step 5: Full Build

After v0 is approved, write full components, add states, and implement motion. Follow the technical specifications and design principles below. 🛑 Checkpoint 3: When you hit a non-trivial decision point during the build (interaction approach choice, content variant, fundamental layout shift), pause and confirm again — don't silently push through.

08
Step 6: Verification

Walk through the "Pre-delivery Checklist" item by item.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.