skills.rest
nghyane
nghyaneCOMMUNITY
Explore all skills by this author →
Website𝕏@nghyaneGitHub

rfc

Creates, updates, and implements RFC documents for cross-cutting frontend UI changes.

3|1|Updated Jan 12, 2026
Search Tags:#documentation#frontend#specification#design tokens#rfc#implementation tracking#ui conventions
One-click install
npx skills add https://github.com/nghyane/VSTEP --skill rfc-nghyane
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rfc
Source: https://github.com/nghyane/VSTEP/tree/main/apps/_deprecated/frontend-v2/.agents/skills/rfc
Command: npx skills add https://github.com/nghyane/VSTEP --skill rfc-nghyane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Cross-cutting UI/UX changes like design tokens, layout conventions, and navigation flows need a formal specification before coding, but teams often skip documentation or lose track of implementation status. This Skill enforces a structured RFC workflow so every major frontend change is proposed, tracked, and verified. ## Core Features & Use Cases - RFC Creation: Generates a new numbered RFC from the standard template, including metadata, motivation, and a concrete violation list with file paths and current vs. expected values. - Status Lifecycle Management: Tracks RFC states (Draft, Accepted, Implemented, Superseded, Withdrawn) and keeps the index in docs/rfcs/README.md synchronized. - Guided Implementation: Walks through the RFC checklist, verifies each fix with grep to confirm violations are gone, and marks the RFC Implemented when complete. - Use Case: When you decide to change the color system across the app, ask the agent to write an RFC first—it scans the codebase for violations, documents them, and later verifies each fix. ## Quick Start Ask the agent to create an RFC for changing the design token system, and it will scan the codebase, draft the spec, and update the RFC index.

Frequently Asked Questions about rfc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an RFC for a frontend design change?▼

Read the RFC index to find the next number, copy the template, and fill in summary, motivation, and a violation list with exact file paths and current versus expected values. Then update the index table with the new entry.

When does a UI change need an RFC?▼

An RFC is required for design token, color, typography, layout, navigation flow, or cross-cutting system changes like coins and notifications. Local bug fixes, new isolated components, mock data updates, and copy edits do not need one.

What are the RFC status values and their meanings?▼

Draft means under discussion, Accepted means approved and in progress, Implemented means fully shipped, Superseded means replaced by another RFC, and Withdrawn means abandoned. Status updates happen as the work progresses.

How do I verify an RFC implementation is complete?▼

Work through the checklist in priority order, and after each file fix run grep to confirm no violations remain. Tick each checkbox as you go, and switch the status to Implemented only when every item is done.

Can I write an RFC without scanning the codebase first?▼

No. The workflow requires evidence from a code scan before drafting, so the violation list contains real file paths, current values, and proposed replacements rather than brainstorming ideas.

Related Skills

Explore More Software Engineering Skills→
microlinkhqmicrolinkhq
142

extract

Extract reusable UI components, tokens, and patterns from a codebase.

Official
Advanced
enkira-aienkira-ai
2

rfc-loop

Chunk an RFC into an Epic and sub-issues, then execute a branch-to-merge loop per chunk.

Official
Advanced
fpindejfpindej
230

review-pr

Review pull requests for production-readiness against project conventions.

Community
Advanced
ehtbantonehtbanton

stylelint-config-generator

Generate Stylelint configuration files for CSS/SCSS linting and formatting.

Community
Basic