plan-design-review

An agent skill by garrytan, from garrytan/gstack. Tags: design, planning, review, ui-ux.

What it does

Designer's eye plan review — interactive, like CEO and Eng review. (gstack)

Install

With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:

npx skills add garrytan/gstack --skill plan-design-review

Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):

git clone --depth 1 https://github.com/garrytan/gstack
cp -r gstack/plan-design-review ~/.claude/skills/plan-design-review

Safety box score

Grade F, high risk: 74 of 100 risk points, rated 2026-10-16. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.

This skill is a powerful plan-review and design-workflow tool: it reads repo context, edits the plan/report, writes artifacts under `~/.gstack`, and can generate mockups and review logs automatically. The main risks are broad filesystem reach, optional data egress to external Codex review, and instruction-heavy behavior that can bypass normal confirmation gates.

Category levels, from 0 (none) to 3 (high)
Category	Level	Why
Code & shell execution	2 (moderate)	It shells out repeatedly (`bash`, `codex exec`, `curl`, `rm -rf`) and runs helper binaries, but the commands are workflow helpers rather than arbitrary downloaded code.
Network access	3 (high)	The outside-voice path can send the plan file and repository context to an external Codex review, and the board flow posts reload requests over HTTP.
Filesystem reach	3 (high)	It edits the plan/report, writes artifacts under `$GSTACK_STATE_ROOT/projects/$SLUG/designs/`, touches `~/.claude` and `.git/info/exclude`, and deletes temp trees.
Secrets & credentials	1 (low)	It probes auth state and can surface cross-project learnings, but the reviewed files do not show direct reads of token stores, keychains, or browser sessions.
Privilege & persistence	2 (moderate)	It mutates git/user-level settings such as `.git/info/exclude` and `gstack-config`, so it changes behavior outside the checked-out repo.
Instruction hijack surface	3 (high)	It tells the agent to auto-select in spawned sessions, honor instruction blocks from tool output, and explicitly says `Do not ask permission`, which is a strong confirmation-bypass surface.
Irreversible actions	2 (moderate)	It can generate mockups immediately, rewrite the plan/report, and auto-decide in spawned or unattended modes, so a single run can materially change planning artifacts.
Transparency	2 (moderate)	Core steps depend on uninspected helper binaries like `~/.claude/skills/gstack/bin/gstack-skill-start` and `design/dist/design`, so part of the behavior is not visible in the reviewed files.

Before installing

Read the Step 0.5 and outside-voices sections if you do not want auto-generated mockups or third-party review prompts.
Verify you are okay with writes under `~/.gstack/`, `~/.claude/`, and `.git/info/exclude`.
Confirm the helper binaries under `~/.claude/skills/gstack/bin/` and `design/dist/design` are installed and trusted.
If plan text must stay local, disable the outside-voice/Codex path before using the skill.

Rated 2026-10-16 by an automated review of 4 files from the skill's repository.

Source

Repository: garrytan/gstack (all skills from this repository)
Path: plan-design-review/SKILL.md
Branch: main
Updated: 2026-10-05

expo-design-system — Framework (OSS). Build and maintain a design system inside an Expo app - a reusable theme of design tokens (color, spacing, typography, radius, shadow.
design-review — Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. (gstack)
ios-design-review — Visual design audit for iOS apps on real hardware. (gstack)
emil-design-eng — This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
architect — Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in.
expo-native-ui — Framework (OSS). Build beautiful, native-feeling Expo screens.