starlight-web-production

Files (3)

• SKILL.md
• openai.yaml · agents/
• technology-lanes.md · references/

SKILL.md (first lines)

# Starlight Web Production

Treat distinctive quality as a release property. A framework, component library, screenshot, or animation technique is evidence or material—not the design direction.

## Authority

Read the owning repository's constitution, `AGENTS.md`, `taste.md`, `design.md` or `DESIGN.md`, tokens, components, analytics, and prior decision receipts. The order of authority is:

1. product truth and brand constitution;
2. repository-local design contract;
3. approved taste/reference records;
4. a locked primary reference and bounded secondary references;
5. live research;
6. model defaults.

Never let Aceternity, GSAP, Refero, shadcn, a template, or a trend become the brand.

## Operating sequence

1. Capture the current desktop and mobile truth. For greenfield work, capture the host context and gather real product states, proof, media, and copy.
2. State one recipient, one job, one promise, one action, one signature proof, and the intended feeling/understanding.
3. Research before composition. Prefer Refero styles/screens/flows when available; otherwise use current public, attributable sources. Record URL, owner, date, rights, observed principle, bounded use, and anti-reference.
4. For consequential visual work, produce exactly three materially different directions using the same real content. Resolve composition, type, imagery, interaction, motion posture, feasibility, and mobile behavior.
5. Record the selected direction. When the user explicitly delegates direction, select the highest-scoring option and record why; otherwise obtain the decision before implementation.
6. Establish static hierarchy, copy, proof, tokens, responsive behavior, and conversion path before motion.
7. Choose the smallest technology lane that expresses the selected direction. Read [technology-lanes.md](references/technology-lanes.md) before adding UI or motion dependencies.
8. Implement against the existing framework and design system. Do not rewrite a stack merely to reach a preferred library.
9. Render and inspect desktop, mobile, interactive, loading/error, and reduced-motion states. Test keyboard order, focus, contrast, reflow, links, claims, privacy, analytics, performance, and failures proportional to the surface.
10. Record commit, checks, preview, production URL, post-deploy inspection, rollback, and the preference receipt.

## Reference lock

Before substantial implementation, record:

```text
Primary foundation:
Preserve:
Secondary reference -> one bounded job:
Media strategy and rights:
Component lane:
Motion lane and named job:
Reject:
Token commitments:
Decision owner:
```

One source owns the foundation. Secondary sources never get averaged into generic premium minimalism.

## Release gates

Block promotion when the surface lacks a current visual capture, real product proof, an explicit reference lock, mobile composition, reduced-motion behavior, accessible interaction, or a production rollback. Copy-paste components must be restyled into owned tokens and inspected for dependencies, semantics, responsiveness, performance, and license boundaries.

Motion must orient, explain, confirm, reveal causality, or create one brand memory. A marketing surface normally earns at most one signature sequence. Do not animate multiple libraries against the same DOM property.

## Output

For builds, return the experience thesis, selected direction, preview, changed artifacts, visual and engineering evidence, verifier verdict, production proof, and rollback. For audits, return current captures, the first three release blockers, the governing rule, the smallest corrective release, and evidence limits.

From frankxai/Starlight-Intelligence-System, MIT.

More from frankxai/Starlight-Intelligence-System