mirror of
https://github.com/boxpositron/absolute-dotfiles.git
synced 2026-10-24 08:23:19 +00:00
David Ibia
ea570af409
- Move the vendored skills from .config/opencode/skills to .config/omo/skills, with provenance and local changes in its README - Rewrite Impeccable's script paths to ~/.omo/agent/skills/impeccable so its detector and live-server verbs resolve under omo - frontend-workflow hands screenshots to a visual-engineering task instead of opencode run - Move the notes commands and /impeccable to .config/omo/prompts as omo prompt templates; setup-mcp stays behind because it writes opencode.json - Archive DEVELOPMENT-WORKFLOW.md and UI-WORKFLOW.md under .config/omo/archive; nothing loads them - link-ai-configs.sh links the skills into omo and Claude Code only and stops linking OpenCode's config, TUI, plugins and workflow docs - setup-mac.sh and Brewfile.apps stop installing OpenCode; README and .withcontextconfig.jsonc follow the new layout ~/.config/opencode/AGENTS.md stays linked: omo's rules engine reads it before ~/.claude/CLAUDE.md and stops at the first hit, so it carries the shared preferences and keeps OMC's instructions out of omo.
6 lines
1.0 KiB
Markdown
6 lines
1.0 KiB
Markdown
# Substantive UI work
|
|
|
|
For interface implementation, redesign, or substantial styling, load `frontend-workflow` on demand before editing. Do not load its body or all design skills for unrelated work. With OMO, delegate implementation through `visual-engineering`, including the brief, design context/reference paths, acceptance criteria, run command, phase, and sole writer's file ownership. A direct GPT worker may perform the same sequential passes without another agent.
|
|
|
|
The user's brief and established product design system override stylistic bans, mandatory decorative treatments, unnecessary research, and arbitrary perfect-score requirements in optional design skills. Fonts, gradients, cards, and motion must serve the product. Respect explicit time/phase limits; do not turn a small resolved brief into a planning ceremony. Never count a screenshot filename, DOM snapshot, or tool success as visual inspection: deliver and inspect image pixels with the GPT worker. Use a normally three-pass maximum and report what remains.
|