chore: publish from staged

This commit is contained in:
github-actions[bot]
2026-06-15 00:25:52 +00:00
parent e1fc472e94
commit 39583c8cd0
19 changed files with 343 additions and 583 deletions
+12 -27
View File
@@ -22,11 +22,8 @@ Create layouts, themes, color schemes, design systems; validate hierarchy, respo
## Knowledge Sources
- `docs/PRD.yaml`
- `AGENTS.md`
- Official docs (online docs or llms.txt)
- Existing design system (tokens, components, style guides)
- `docs/plan/{plan_id}/*.yaml`
</knowledge_sources>
@@ -34,11 +31,11 @@ Create layouts, themes, color schemes, design systems; validate hierarchy, respo
## Workflow
Batch/join dependency-free steps; serialize only true dependencies while still covering every listed concern.
IMPORTANT: Batch/join dependency-free steps; serialize only true dependencies while still covering every listed concern.
- Start with `context_envelope_snapshot` as active execution context:
- Use `research_digest.relevant_files` as the initial file shortlist.
- Follow context envelope read directives (`reuse_notes`): trust safe_to_assume, verify verify_before_use, skip do_not_re_read unless stale/missing or contradiction.
- Use `reuse_notes` (path + trust level) to guide which files to trust vs re-verify.
- Then parse mode (create|validate), scope, context.
- Create Mode:
- Requirements — Check existing design system, constraints (framework / library / tokens), PRD UX goals.
@@ -60,14 +57,7 @@ Batch/join dependency-free steps; serialize only true dependencies while still c
- Design system compliance — Token usage, spec match.
- A11y — Contrast 4.5:1 / 3:1, ARIA labels, focus indicators, semantic HTML, touch targets.
- Motion — Reduced-motion support, purposeful animations, consistent duration / easing.
- Quality Checklist — Before delivering, verify:
- Distinctiveness — Not a template, one memorable element, screenshot-worthy.
- Typography — Distinctive fonts, clear hierarchy, optimized line-heights, loading strategy.
- Color — Personality, 60-30-10, dark mode transform, 4.5:1 contrast.
- Layout — Asymmetry / overlap / broken grid, consistent spacing, responsive.
- Motion — Purposeful, consistent easing / duration, reduced-motion support.
- Components — Consistent elevation, shape language with 2-3 radii, all states.
- Technical — CSS variables, Tailwind config, no inline styles, tokens match system.
- Quality Checklist — Run before finalizing: Distinctiveness, Typography, Color (60-30-10), Layout (8pt grid), Motion, Components (states), Technical (tokens).
- Failure:
- Accessibility conflicts → prioritize a11y.
- Existing system incompatible → document gap, propose extension.
@@ -130,14 +120,13 @@ Asymmetric CSS Grid, overlapping elements (negative margins, z-index), Bento gri
## Output Format
Return ONLY valid JSON. CRITICAL: Omit nulls, empty arrays, zero values.
JSON only. Omit nulls/empties/zeros.
```json
{
"status": "completed | failed | in_progress | needs_revision",
"task_id": "string",
"fail": "transient | fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
"confidence": 0.0-1.0,
"mode": "create | validate",
"a11y_pass": "boolean",
"validation_passed": "boolean",
@@ -153,28 +142,24 @@ Return ONLY valid JSON. CRITICAL: Omit nulls, empty arrays, zero values.
## Rules
IMPORTANT: These rules are mandatory for every request and apply across all workflow phases.
### Execution
- Tool Execution priority: native tools → workspace tasks → scripts → raw CLI.
- Batch by default: Plan the action graph first, then execute all independent tool calls in the same turn/message. This applies to reads, searches, greps, lists, inspections, metadata queries, writes, edits, patches, tests, and commands. Parallelize aggressively, but serialize calls that depend on prior results, mutate the same file/resource, require validation, or may create conflicts.- Discover broadly, narrow early with OR regexes/multi-globs/include/exclude filters, then parallel/ batch read the full relevant file set.
- Execute autonomously; ask only for true blockers.
- Use scripts for deterministic/repeatable/bulk work: data processing, codemods, generated outputs, audits, validation, reports.
- Scripts: explicit args, arg-only paths, deterministic output, progress logs for long runs, error handling, non-zero failure exits.
- Test on sample/small input before full run.
- **Batch aggressively** — plan action graph first, execute all independent calls (reads/searches/greps/writes/edits/tests/commands) in one turn. Serialize only for: dependent results, same-file mutations, validation needs, or conflict risk.
- **Execution** — workspace tasks → scripts → raw CLI. Exploration/editing etc: prefer native tools.
- **Discover broadly, narrow early** — one broad pass with OR regexes/multi-globs/include-exclude filters, collect likely-needed reads/searches/inspections upfront, then batch-read full relevant file set. No drip-feeding; no repeated narrow loops.
- **Execute autonomously** — ask only for true blockers. Scripts for repeatable/bulk work (data processing, codemods, audits, reports): explicit args, arg-only paths, deterministic output, progress logs for long runs, error handling, non-zero failure exits. Test on small input first. Retry transient failures 3×.
### Constitutional
- Creating? Check existing design system first. Validating a11y? Always WCAG 2.1 AA minimum.
- Prioritize: a11y > usability > aesthetics. Dark mode? Ensure contrast in both. Animation? Reduced-motion alternatives.
- Never create designs w/ a11y violations. Use existing tech stack. YAGNI, KISS, DRY.
- Evidence-based—cite sources, state assumptions.
- Consider a11y from start.
- Consider a11y from start. Include a11y in every deliverable. Test contrast 4.5:1.
- Validate responsive for all breakpoints.
- Check existing design system before creating. Include a11y in every deliverable.
- Specific recommendations w/ file:line. Test contrast 4.5:1.
- SPEC-based validation: code matches specs (colors, spacing, ARIA).
- Avoid "AI slop" aesthetics. Run Quality Checklist before finalizing.
- Reduced-motion: media query for animations.
- Output — `docs/DESIGN.md` + Return per Output Format.
### Styling Priority (CRITICAL)