Rayden Code

Rayden Code Skill

Overview

This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/rayden-code from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.

Rayden Code Skill

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: How It Works, Security & Safety Notes, Common Pitfalls, Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• You're building a new page or feature using Rayden UI components
• You want to scaffold a dashboard, landing page, auth screen, settings page, or data table
• You need to generate React code that follows a specific design system precisely
• You want to prototype UI quickly with correct component usage and premium aesthetics
• You're vibe coding and want design-system-compliant output
• Use when the request clearly matches the imported source intent: Generate React code with Rayden UI components using correct props, tokens, and premium layout patterns.

Operating Table

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
2. Read the overview and provenance files before loading any copied upstream support files.
3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
5. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: Overview

Generate production-quality React + Tailwind CSS code using the Rayden UI component library (34 components). The skill loads a complete API reference with every component, every prop, design tokens, layout patterns, and an explicit anti-pattern ban list — preventing hallucinated components and generic AI output. Built on the Rayna UI design system.

Imported: How It Works

1. Parses the request — Identifies page type, required components, and data model
2. Loads RAYDEN_RULES.md — Complete reference: 34 components with full props, design philosophy, token classes, layout patterns, anti-patterns, and accessibility rules
3. Plans the layout — Decides page structure, component selection, spacing, color, and elevation strategy
4. Generates code — Writes React + Tailwind CSS using only documented components and token classes
5. Self-validates — Runs a 16-point checklist covering correctness (valid components/props, token usage, nesting) and design quality (whitespace, hierarchy, restraint, responsiveness)

Examples

Example 1: Ask for the upstream workflow directly

Use @rayden-code to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @rayden-code against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @rayden-code for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @rayden-code using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Imported Usage Notes

Imported: Examples

Vibe code a SaaS dashboard

/rayden-code a dashboard with KPI cards, a recent orders table, and an activity feed

Use case: You're building an internal analytics tool and need a full dashboard page with MetricsCard grid, sortable Table, and ActivityFeed sidebar — all with correct Rayden imports and token classes.

Scaffold a login page

/rayden-code login page with email and password

Use case: You need a centered auth form with Input components, a primary Button, and proper visual hierarchy — following Rayden's "Auth / Focused Form" pattern.

Build an admin settings page

/rayden-code settings page with profile section, notification toggles, and danger zone

Use case: You're adding a settings area to your app and need form sections with Toggle components, a destructive action zone, and a single-column constrained layout.

Create a pricing page

/rayden-code pricing page with 3 tiers and a feature comparison table

Use case: You need a marketing pricing section with Card components for each tier, Badge for the recommended plan, and a Table for feature comparison.

Build an e-commerce product grid

/rayden-code product catalog with filters, search, and a card grid

Use case: You're building a storefront and need a responsive product grid with Chip filters, Input search, Pagination, and Cards with images — all using Rayden's layout and spacing rules.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Describe what you want in plain language — the skill maps your request to the right components
• Install @raydenui/ui in your project first (npm install @raydenui/ui)
• Import @raydenui/ui/styles.css in your app entry point for design tokens to work
• Review generated code for business logic — the skill handles UI, not data fetching
• Use alongside /rayden-use if you also want the same design built in Figma
• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.

Imported Operating Notes

Imported: Best Practices

• Describe what you want in plain language — the skill maps your request to the right components
• Install @raydenui/ui in your project first (npm install @raydenui/ui)
• Import @raydenui/ui/styles.css in your app entry point for design tokens to work
• Review generated code for business logic — the skill handles UI, not data fetching
• Use alongside /rayden-use if you also want the same design built in Figma

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/rayden-code, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

Imported Reference Notes

Imported: Security & Safety Notes

• This skill only reads its bundled rules file and writes code to your project
• No external network requests
• No secrets or credentials involved
• Generated code uses standard React patterns with no eval or dynamic code execution

Imported: Common Pitfalls

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.