Execute approved plans into working frontend code with accessibility and UX consistency.
npx skills add https://github.com/HakAl/team_skills --skill greenfield-gary
Please help me install this Agent Skill. Skill: greenfield-gary Source: https://github.com/HakAl/team_skills/tree/main/greenfield-gary Command: npx skills add https://github.com/HakAl/team_skills --skill greenfield-gary
Greenfield Gary is the Builder and UX Guru. Executes approved plans, turning designs into working code. Expert in accessibility, internationalization, and UX patterns across platforms. Optimistic but disciplined - follows the plan. Invoke with "Gary, build this".
Provide an approved plan and say "Gary, build this" to begin execution.
High-intent search queries and answers about installing and using this skill.
To turn an approved frontend plan into accessible working code, provide the validated plan and trigger execution. The process enforces plan-guardrails, immutability rules, and validation steps to ensure QA and user testing adherence.
Plan-driven UX development is a workflow where an approved design plan dictates user interface implementation. It maintains UX consistency by enforcing immutability rules and validation steps during code generation.
Yes, you can use this builder for frontend internationalization and accessible UX patterns. It provides guidance on user-centric design across platforms, ensuring features meet accessibility standards during plan execution.
The best way to execute a validated software plan while enforcing QA adherence is using a structured protocol with validation steps. This ensures generated code respects plan-guardrails and immutability rules throughout feature development.
Yes, you need a fully approved plan before starting frontend feature development. The builder acts as an implementer from a validated plan, ensuring generated code strictly follows established guardrails and design specifications.
i3ringitAnalyze specifications to map user flows, edge cases, and gaps.
jhlee0409Review TypeScript and React code for quality, accessibility, and performance.
HakAlOrchestrate Plan–Critique–Build–Validate team improvement cycles from .team/TEAM.md protocols.
AvihusittonEnforce anti-generic design rules for React and Next.js frontend interfaces.
