opencodekit 0.21.10 → 0.23.0

package/dist/template/.opencode/command/ui-slop-check.md

@@ -1,169 +0,0 @@
----
-description: Audit changed UI files for AI slop patterns and design-system violations
-argument-hint: "[path|auto] [--staged] [--since=<ref>] [--full-report]"
-agent: vision
-model: proxypal/gemini-3-pro-preview
----
-
-# UI Slop Check: $ARGUMENTS
-
-Run a focused anti-slop audit against changed UI files using the frontend-design taxonomy.
-
-## Load Skills
-
-```typescript
-skill({ name: "frontend-design" }); // Anti-pattern taxonomy + design references
-skill({ name: "visual-analysis" }); // Structured visual/code analysis workflow
-skill({ name: "accessibility-audit" }); // Keyboard/focus/contrast checks
-skill({ name: "ux-quality-gates" }); // UX correctness gates beyond visual slop
-```
-
-## Parse Arguments
-
-| Argument        | Default | Description                                                 |
-| --------------- | ------- | ----------------------------------------------------------- |
-| `[path\|auto]`  | `auto`  | Specific file/dir to audit, or auto-detect changed UI files |
-| `--staged`      | false   | Audit staged changes only (`git diff --cached`)             |
-| `--since=<ref>` | `HEAD`  | Compare against ref (`main`, `HEAD~1`, commit SHA)          |
-| `--full-report` | false   | Include all categories even when no issues found            |
-
-## Phase 1: Resolve Target Files
-
-If `[path]` is provided:
-
-- Audit that path directly
-
-If `auto`:
-
-```bash
-# unstaged + staged by default
-git diff --name-only $SINCE_REF -- \
-  '*.tsx' '*.jsx' '*.css' '*.scss' '*.sass' '*.less' '*.html' '*.mdx'
-```
-
-If `--staged`:
-
-```bash
-git diff --cached --name-only -- \
-  '*.tsx' '*.jsx' '*.css' '*.scss' '*.sass' '*.less' '*.html' '*.mdx'
-```
-
-Prioritize files under:
-
-- `src/components/**`
-- `src/app/**`
-- `src/pages/**`
-- `app/**`
-- `components/**`
-
-If no UI files changed, return: **PASS (no changed UI files)**.
-
-## Phase 2: Run AI Slop Checklist
-
-Evaluate each target file (or rendered screenshot if provided) against these checks.
-
-### A) Typography
-
-- Banned default aesthetics (Inter/Roboto/Arial/Open Sans as dominant display voice)
-- Body text uses `rem/em`, not fixed `px`
-- Clear hierarchy (size/weight/spacing), not color-only hierarchy
-- Body line length near readable measure (around 65ch when applicable)
-
-### B) Color and Theming
-
-- No AI default palette tropes (purple-blue gradient defaults, neon-on-dark clichés)
-- No pure `#000` / `#fff` as dominant surfaces
-- Gray text is not placed on saturated backgrounds
-- Semantic tokens are used (not random per-component hardcoded colors)
-- Dark mode is adapted, not simple inversion
-
-### C) Layout and Spatial Rhythm
-
-- No cards-inside-cards without strong information architecture reason
-- No repetitive cookie-cutter card blocks with identical structure
-- Spacing rhythm is consistent (4pt-style cadence), not arbitrary jumps
-- Uses `gap`/layout primitives cleanly; avoids margin hacks when possible
-
-### D) Motion and Interaction
-
-- No bounce/elastic gimmick motion for product UI
-- Animations use transform/opacity (avoid layout-thrashing properties)
-- Reduced motion support exists for meaningful motion
-- States exist: hover, focus-visible, active, disabled, loading/error where relevant
-
-### E) UX Writing
-
-- Buttons are verb + object (e.g. "Save changes")
-- Error copy includes what happened + why + how to fix
-- Empty states include guidance + next action
-- Terminology is consistent (avoid mixed synonyms for same action)
-- User-facing labels avoid implementation terms, database names, and internal acronyms
-
-### F) UX Quality Gates
-
-- One dominant filled primary action per view/section
-- Destructive actions require explicit confirm or undo, with specific entity/count in copy
-- No placeholder-as-label form fields
-- Form errors are associated with controls (`aria-describedby`, `aria-invalid`, `role="alert"`)
-- Submit/loading states prevent double-submit without layout shift
-- Empty, loading, error, and success states exist where async/data flows exist
-- Error toasts/banners persist long enough and include retry/undo/support where applicable
-- Data-heavy UI distinguishes empty state from filtered no-results state
-- Bulk actions show selected count and confirm destructive scope
-
-### G) Accessibility Safety Nets
-
-- Keyboard-visible focus treatment (`:focus-visible`)
-- Contrast baseline expectations (WCAG AA)
-- Touch targets reasonable (44x44 context where applicable)
-- Native semantic elements are used before ARIA patches (`button`, `a`, `form`, landmarks)
-- Heading structure has one logical `h1` per page/screen context
-
-### H) Component Family Consistency
-
-- Buttons and inputs in the same form share height, radius, border, and focus treatment
-- Focus, error, disabled, and loading states use the same token logic across components
-- No one-off radius/shadow/border width unless documented as a system-level exception
-- Semantic color roles are consistent: success, warning, destructive, info, primary
-
-## Phase 3: Severity and Scoring
-
-Group findings by severity:
-
-- **Critical**: accessibility failures, broken interaction states, unreadable contrast
-- **Warning**: strong AI fingerprint/slop patterns, inconsistent design system usage
-- **Info**: polish/consistency opportunities
-
-Score each category 1-10 and include evidence (`file:line` for code audits).
-
-## Phase 4: Output
-
-Return:
-
-1. **Result**: PASS / NEEDS WORK
-2. **Audited files** (list)
-3. **Category scores**
-4. **Findings by severity** with actionable fixes
-5. **Fast remediation plan** (top 3 fixes first)
-
-If `--full-report` is false, omit empty categories.
-
-## Record Findings
-
-```typescript
-observation({
-  type: "warning",
-  title: "UI Slop Check: [scope]",
-  narrative: "Detected [count] critical, [count] warning slop issues in changed UI files.",
-  concepts: "ui, design, anti-patterns, frontend",
-  confidence: "high",
-});
-```
-
-## Related Commands
-
-| Need                                     | Command      |
-| ---------------------------------------- | ------------ |
-| Design from scratch                      | `/design`    |
-| Full UI review (single screen/component) | `/ui-review` |
-| Implementation work                      | `/ship`      |

package/dist/template/.opencode/plans/1768385996691-silent-wizard.md

@@ -1,247 +0,0 @@
-# Plan: Optimize Scout Agent for External Research
-
-**Goal:** Enhance Scout agent prompt with missing tool integrations and workflows for optimal external research.
-
-**Scope:** READ-ONLY external research only (no local codebase changes)
-
----
-
-## Changes Required
-
-### File: `.opencode/agent/scout.md`
-
-#### 1. Add Memory-First Protocol (after line 43, before "External research:")
-
-````markdown
-## Memory First
-
-Before hitting external APIs, check past research:
-
-```typescript
-memory - search({ query: "<topic keywords>", limit: 3 });
-```
-````
-
-If memory returns high-confidence findings on this exact topic, synthesize and return without external calls. Only proceed to external sources if:
-
-- No relevant memory found
-- Memory findings are outdated or low-confidence
-- Question requires fresher data
-
-````
-
-#### 2. Add Tool Priority Section (replace/enhance "## Guidelines" around line 88)
-
-```markdown
-## Tool Priority (External Sources Only)
-
-| Priority | Tool | Use Case | Speed |
-|----------|------|----------|-------|
-| 1 | memory-search | Past research findings | Instant |
-| Priority | Tool | Use Case | Speed |
-|----------|------|----------|-------|
-| 1 | memory-search | Past research findings | Instant |
-| 2 | context7_resolve-library-id | Resolve library names to IDs | Fast |
-| 3 | context7_query-docs | Official library docs | Fast |
-| 4 | codesearch | Exa Code API for SDK/library patterns | Fast |
-| 5 | grepsearch | Cross-repo GitHub code search | Medium |
-| 6 | webfetch | Specific doc URLs, READMEs, changelogs | Medium |
-| 7 | opensrc + LSP | Clone & analyze source code | Slow |
-| 8 | websearch | Tutorials, blog posts, recent news | Slow |
-| 3 | codesearch | Usage patterns in real code | Fast |
-| 4 | gh_grep | Cross-repo deep code search | Medium |
-| 5 | webfetch | Specific doc URLs, READMEs, changelogs | Medium |
-| 6 | opensrc + LSP | Clone & analyze source code | Slow |
-| 7 | websearch | Tutorials, blog posts, recent news | Slow |
-
-**Rule:** Exhaust faster tools before slower ones. Run tools in parallel when independent.
-````
-
-#### 3. Add webfetch Section (new section after Tool Priority)
-
-````markdown
-## webfetch Usage
-
-Use `webfetch` for specific external URLs when you have a known target:
-
-```typescript
-// GitHub raw files
-webfetch({
-  url: "https://raw.githubusercontent.com/owner/repo/main/README.md",
-  format: "markdown",
-});
-
-// Documentation pages
-webfetch({ url: "https://zod.dev/docs/guides/async", format: "markdown" });
-
-// Release notes
-webfetch({ url: "https://github.com/colinhacks/zod/releases", format: "markdown" });
-
-// API references
-webfetch({ url: "https://docs.example.com/api/authentication", format: "markdown" });
-```
-````
-
-**When to use:**
-
-- User provides a specific URL
-- context7_resolve-library-id returns a library ID
-- context7_query-docs returns a doc link worth fetching
-- Need CHANGELOG or release notes
-- GitHub README has details not in context7
-
-````
-
-#### 4. Add Source Code Deep Dive Section (new section, expand on existing clone guidance)
-
-```markdown
-## Source Code Deep Dive
-
-When documentation is insufficient, analyze actual source code.
-
-### Step 1: Load the Skill
-```typescript
-skill({ name: "source-code-research" })
-````
-
-### Step 2: Clone the Package
-
-```bash
-npx opensrc <package>           # npm (auto-detects version)
-npx opensrc <package>@<version> # specific version
-npx opensrc pypi:<package>      # Python
-npx opensrc <owner>/<repo>      # GitHub repo
-```
-
-### Step 3: Navigate with LSP
-
-After cloning, source lands in `opensrc/repos/github.com/<owner>/<repo>/`. Use LSP:
-
-```typescript
-// Get file structure
-lsp({
-  operation: "documentSymbol",
-  filePath: "opensrc/repos/.../src/index.ts",
-  line: 1,
-  character: 1,
-});
-
-// Jump to definition
-lsp({
-  operation: "goToDefinition",
-  filePath: "opensrc/repos/.../src/types.ts",
-  line: 42,
-  character: 10,
-});
-
-// Find all usages
-lsp({
-  operation: "findReferences",
-  filePath: "opensrc/repos/.../src/core.ts",
-  line: 100,
-  character: 5,
-});
-```
-
-### Step 4: Search Within Clone
-
-```typescript
-// Find specific patterns
-grep({ pattern: "async.*refine", path: "opensrc/", include: "*.ts" });
-
-// Check tests for usage examples
-glob({ pattern: "opensrc/**/test/**/*.ts" });
-glob({ pattern: "opensrc/**/*.test.ts" });
-```
-
-### Step 5: Construct Permalinks
-
-Build GitHub permalinks from cloned code:
-
-```
-https://github.com/<owner>/<repo>/blob/<sha>/path/to/file.ts#L42-L56
-```
-
-Get SHA from `opensrc/sources.json` or the cloned repo.
-
-````
-
-#### 5. Update Fallback Chain in "When Things Fail" Section (enhance existing)
-
-```markdown
-## When Things Fail
-
-### Fallback Chain
-````
-
-context7 fails → try codesearch for patterns
-codesearch empty → try gh_grep with broader query
-gh_grep empty → webfetch specific doc URLs if known
-still stuck → opensrc clone + LSP analysis
-last resort → websearch for tutorials/blogs
-
-```
-
-### Specific Failures
-
-**context7 doesn't find library:**
-1. Try `codesearch({ query: "<library> <function> example" })`
-2. Try `gh_grepsearchGitHub({ query: "import.*from.*<library>" })`
-3. Clone with `npx opensrc <library>` and read source
-
-**gh_grep returns nothing:**
-- Broaden query: search concepts, not exact function names
-- Try different language filters
-- Search for error messages or config patterns
-
-**opensrc clone fails:**
-- Check if package exists on npm/pypi/crates
-- Try GitHub URL directly: `npx opensrc owner/repo`
-- Fall back to `webfetch` on raw GitHub files
-
-**API rate limits:**
-- Work from already-cloned repos in `opensrc/`
-- Use `memory-search` to find cached findings
-- Reduce parallel calls, go sequential
-```
-
----
-
-## Summary of Additions
-
-| Addition                | Lines | Purpose                                   |
-| ----------------------- | ----- | ----------------------------------------- |
-| Memory-First Protocol   | ~15   | Check past research before external calls |
-| Tool Priority Table     | ~15   | Clear hierarchy for tool selection        |
-| webfetch Section        | ~25   | Document missing tool usage               |
-| Source Code Deep Dive   | ~50   | Full opensrc + LSP workflow               |
-| Enhanced Fallback Chain | ~30   | Clear failure recovery paths              |
-
-**Total additions:** ~135 lines
-
----
-
-## Files to Modify
-
-1. `.opencode/agent/scout.md` - Add sections above
-
----
-
-## Verification
-
-After implementation:
-
-1. Test Quick Mode: `@scout how to use zod .refine()`
-2. Test Deep Mode: `@scout how do production apps handle zod async validation`
-3. Test Source Dive: `@scout show me zod's internal parse implementation`
-4. Verify memory check appears in scout's first actions
-5. Verify webfetch used when given specific URLs
-
----
-
-## Out of Scope
-
-- Local codebase access (that's Explore agent)
-- File modifications outside `.beads/artifacts/`
-- Question tool (subagent constraint)
-- New MCP integrations (uses existing tools)