design-review

Name: design-review
Author: tranhieutt

69stars41forks

How to install design-review?

tranhieutt/software_development_department/design-review

$npx -y skills add tranhieutt/software_development_department --skill design-review

Installs into the current project.

Summary

Reviews UI/UX designs, wireframes, and design systems for usability, accessibility, consistency, and implementation feasibility. Use when reviewing design specs or when the user mentions design review, UX review, or design feedback.

Files · 1

View on GitHub

SKILL.md

1	When this skill is invoked:
2
3	1. Read the target design document in full.
4
5	2. Read the master CLAUDE.md to understand project context and standards.
6
7	3. Read related design documents referenced or implied by the target doc
8	(check `design/docs/` for related systems).
9
10	4. Evaluate against the Design Document Standard checklist:
11	- [ ] Has Overview section (one-paragraph summary)
12	- [ ] Has User Fantasy section (intended feeling)
13	- [ ] Has Detailed Rules section (unambiguous mechanics)
14	- [ ] Has Formulas section (all math defined with variables)
15	- [ ] Has Edge Cases section (unusual situations handled)
16	- [ ] Has Dependencies section (other systems listed)
17	- [ ] Has Tuning Knobs section (configurable values identified)
18	- [ ] Has Acceptance Criteria section (testable success conditions)
19
20	5. Check for internal consistency:
21	- Do the formulas produce values that match the described behavior?
22	- Do edge cases contradict the main rules?
23	- Are dependencies bidirectional (does the other system know about this one)?
24
25	6. Check for implementability:
26	- Are the rules precise enough for a programmer to implement without guessing?
27	- Are there any "hand-wave" sections where details are missing?
28	- Are performance implications considered?
29
30	7. Check for cross-system consistency:
31	- Does this conflict with any existing mechanic?
32	- Does this create unintended interactions with other systems?
33	- Is this consistent with the product's established tone and pillars?
34
35	8. Output the review in this format:
36
37	```
38	## Design Review: [Document Title]
39
40	### Completeness: [X/8 sections present]
41	[List missing sections]
42
43	### Consistency Issues
44	[List any internal or cross-system contradictions]
45
46	### Implementability Concerns
47	[List any vague or unimplementable sections]
48
49	### Balance Concerns
50	[List any obvious balance risks]
51
52	### Recommendations
53	[Prioritized list of improvements]
54
55	### Verdict: [APPROVED / NEEDS REVISION / MAJOR REVISION NEEDED]
56	```
57
58	9. Contextual next step recommendations:
59	- If the document being reviewed is `product-concept.md` or `product-pillars.md`:
60	- Check if `design/docs/systems-index.md` exists
61	- If it does NOT exist, add to Recommendations:
62	> "This concept is ready for systems decomposition. Run `/map-systems`
63	> to break it down into individual systems with dependencies and priorities,
64	> then write per-system PRDs."
65	- If the document is an individual system PRD:
66	- Check if the systems index references this system
67	- If verdict is APPROVED: suggest "Update the systems index status for
68	this system to 'Approved'."
69	- If verdict is NEEDS REVISION or MAJOR REVISION NEEDED: suggest "Update
70	the systems index status for this system to 'In Review'."
71	- Note: This skill is read-only. The user (or `/design-system`) must
72	perform the actual status update in the systems index.
73
74	## Protocol
75
76	- Question: Auto-starts from argument (path to design doc)
77	- Options: Skip — single review path
78	- Decision: Skip — verdict is advisory
79	- Draft: Full review shown in conversation only
80	- Approval: Skip — read-only; this skill never writes files
81
82	## Output
83
84	Deliver exactly:
85
86	- Completeness score (X/8 required sections present)
87	- Consistency issues — contradictions or undefined terms (or "None")
88	- Implementability concerns — sections too vague to build from (or "None")
89	- Verdict: `APPROVED` / `NEEDS REVISION` / `MAJOR REVISION NEEDED`
90	- Next skill — one recommended follow-up (e.g., `/map-systems`, update systems index)

People who liked this also viewed

6 picks

Type

design-review

69stars41forks

View on GitHub

How to install design-review?

tranhieutt/software_development_department/design-review

$npx -y skills add tranhieutt/software_development_department --skill design-review

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	When this skill is invoked:
2
3	1. Read the target design document in full.
4
5	2. Read the master CLAUDE.md to understand project context and standards.
6
7	3. Read related design documents referenced or implied by the target doc
8	(check `design/docs/` for related systems).
9
10	4. Evaluate against the Design Document Standard checklist:
11	- [ ] Has Overview section (one-paragraph summary)
12	- [ ] Has User Fantasy section (intended feeling)
13	- [ ] Has Detailed Rules section (unambiguous mechanics)
14	- [ ] Has Formulas section (all math defined with variables)
15	- [ ] Has Edge Cases section (unusual situations handled)
16	- [ ] Has Dependencies section (other systems listed)
17	- [ ] Has Tuning Knobs section (configurable values identified)
18	- [ ] Has Acceptance Criteria section (testable success conditions)
19
20	5. Check for internal consistency:
21	- Do the formulas produce values that match the described behavior?
22	- Do edge cases contradict the main rules?
23	- Are dependencies bidirectional (does the other system know about this one)?
24
25	6. Check for implementability:
26	- Are the rules precise enough for a programmer to implement without guessing?
27	- Are there any "hand-wave" sections where details are missing?
28	- Are performance implications considered?
29
30	7. Check for cross-system consistency:
31	- Does this conflict with any existing mechanic?
32	- Does this create unintended interactions with other systems?
33	- Is this consistent with the product's established tone and pillars?
34
35	8. Output the review in this format:
36
37	```
38	## Design Review: [Document Title]
39
40	### Completeness: [X/8 sections present]
41	[List missing sections]
42
43	### Consistency Issues
44	[List any internal or cross-system contradictions]
45
46	### Implementability Concerns
47	[List any vague or unimplementable sections]
48
49	### Balance Concerns
50	[List any obvious balance risks]
51
52	### Recommendations
53	[Prioritized list of improvements]
54
55	### Verdict: [APPROVED / NEEDS REVISION / MAJOR REVISION NEEDED]
56	```
57
58	9. Contextual next step recommendations:
59	- If the document being reviewed is `product-concept.md` or `product-pillars.md`:
60	- Check if `design/docs/systems-index.md` exists
61	- If it does NOT exist, add to Recommendations:
62	> "This concept is ready for systems decomposition. Run `/map-systems`
63	> to break it down into individual systems with dependencies and priorities,
64	> then write per-system PRDs."
65	- If the document is an individual system PRD:
66	- Check if the systems index references this system
67	- If verdict is APPROVED: suggest "Update the systems index status for
68	this system to 'Approved'."
69	- If verdict is NEEDS REVISION or MAJOR REVISION NEEDED: suggest "Update
70	the systems index status for this system to 'In Review'."
71	- Note: This skill is read-only. The user (or `/design-system`) must
72	perform the actual status update in the systems index.
73
74	## Protocol
75
76	- Question: Auto-starts from argument (path to design doc)
77	- Options: Skip — single review path
78	- Decision: Skip — verdict is advisory
79	- Draft: Full review shown in conversation only
80	- Approval: Skip — read-only; this skill never writes files
81
82	## Output
83
84	Deliver exactly:
85
86	- Completeness score (X/8 required sections present)
87	- Consistency issues — contradictions or undefined terms (or "None")
88	- Implementability concerns — sections too vague to build from (or "None")
89	- Verdict: `APPROVED` / `NEEDS REVISION` / `MAJOR REVISION NEEDED`
90	- Next skill — one recommended follow-up (e.g., `/map-systems`, update systems index)

People who liked this also viewed

6 picks

Type