agemon 6.0.0 → 6.3.0

package/assets/skills/essentials/web-design-guidelines/NOTICE.md

@@ -0,0 +1,14 @@
+# Vendored skill
+
+- Source: https://github.com/vercel-labs/web-interface-guidelines
+- Path in source: command.md
+- Commit: 434b7f91364665f2f733b310ec54809bf8f37937
+- Retrieved: 2026-11-05
+- License: MIT — see `LICENSE` in this directory.
+
+## agemon modifications
+
+- `references/guidelines.md` is upstream's `command.md` with its frontmatter and the `$ARGUMENTS` line removed. The rules and output format are unchanged.
+- `SKILL.md` is agemon's own wrapper. Instead of fetching the guidelines from a URL, it reads `references/guidelines.md`.
+- Judgement call: the wrapper keeps the `name` and the short `description` of the skill agemon installed before, so existing installs are recognised and the skill still routes on the same phrases. That text comes from https://github.com/vercel-labs/agent-skills at commit 063bee94c3f4df8453406c830b0a7df0f2860278 (path `skills/web-design-guidelines/SKILL.md`). That repository's README states MIT, but it has no LICENSE file at that commit, so the licence for this carried-over text is stated, not shipped. The rest of the wrapper is written by agemon.
+- Keeps the name `web-design-guidelines` rather than an `agemon-*` name, so existing installs are recognised and can be updated.

package/assets/skills/essentials/web-design-guidelines/SKILL.md

@@ -0,0 +1,18 @@
+---
+name: web-design-guidelines
+description: Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
+argument-hint: <file-or-pattern>
+---
+
+# Web Interface Guidelines
+
+Review files for compliance with the Web Interface Guidelines.
+
+## How it works
+
+1. Read the files the user named, or ask which files or pattern to review.
+2. Read `references/guidelines.md` next to this file. It holds every rule and the output format.
+3. Check each file against all of the rules.
+4. Report findings in the terse `file:line` format the guidelines specify.
+
+The guidelines ship with this skill at a pinned version. Do not look for newer rules elsewhere.

package/assets/skills/essentials/web-design-guidelines/references/guidelines.md

@@ -0,0 +1,184 @@
+# Web Interface Guidelines
+
+Read files, check against rules below. Output concise but comprehensive—sacrifice grammar for brevity. High signal-to-noise.
+
+## Rules
+
+### Accessibility
+
+- Icon-only buttons need `aria-label`
+- Form controls need `<label>` or `aria-label`
+- Interactive elements need keyboard handlers (`onKeyDown`/`onKeyUp`)
+- `<button>` for actions, `<a>`/`<Link>` for navigation (not `<div onClick>`)
+- Images need `alt` (or `alt=""` if decorative)
+- Decorative icons need `aria-hidden="true"`
+- Async updates (toasts, validation) need `aria-live="polite"`
+- Use semantic HTML (`<button>`, `<a>`, `<label>`, `<table>`) before ARIA
+- Headings hierarchical `<h1>`–`<h6>`; include skip link for main content
+- `scroll-margin-top` on heading anchors
+- Meaningful media needs captions, transcripts, or descriptions as applicable
+- Media controls need keyboard support; decorative media needs assistive-tech hiding
+
+### Focus States
+
+- Interactive elements need visible focus: `focus-visible:ring-*` or equivalent
+- Never `outline-none` / `outline: none` without focus replacement
+- Use `:focus-visible` over `:focus` (avoid focus ring on click)
+- Group focus with `:focus-within` for compound controls
+- Sticky headers/footers/overlays must not cover the focused element
+
+### Forms
+
+- Inputs need `autocomplete` and meaningful `name`
+- Use correct `type` (`email`, `tel`, `url`, `number`) and `inputmode`
+- Never block paste (`onPaste` + `preventDefault`)
+- Labels clickable (`htmlFor` or wrapping control)
+- Disable spellcheck on emails, codes, usernames (`spellCheck={false}`)
+- Checkboxes/radios: label + control share single hit target (no dead zones)
+- Submit button stays enabled until request starts; spinner during request
+- Errors inline next to fields; focus first error on submit
+- Placeholders end with `…` and show example pattern
+- `autocomplete="off"` on non-auth fields to avoid password manager triggers
+- Warn before navigation with unsaved changes (`beforeunload` or router guard)
+
+### Animation
+
+- Honor `prefers-reduced-motion` (provide reduced variant or disable)
+- Animate `transform`/`opacity` only (compositor-friendly)
+- Never `transition: all`—list properties explicitly
+- Set correct `transform-origin`
+- SVG: transforms on `<g>` wrapper with `transform-box: fill-box; transform-origin: center`
+- Animations interruptible—respond to user input mid-animation
+- Autoplay motion >5 seconds alongside other content needs pause, stop, or hide controls
+- Muted decorative loops must stop under `prefers-reduced-motion`
+
+### Typography
+
+- `…` not `...`
+- Curly quotes `“` `”` not straight `"`
+- Non-breaking spaces: `10&nbsp;MB`, `⌘&nbsp;K`, brand names
+- Loading states end with `…`: `"Loading…"`, `"Saving…"`
+- `font-variant-numeric: tabular-nums` for number columns/comparisons
+- Use `text-wrap: balance` or `text-pretty` on headings (prevents widows)
+
+### Content Handling
+
+- Text containers handle long content: `truncate`, `line-clamp-*`, or `break-words`
+- Flex children need `min-w-0` to allow text truncation
+- Handle empty states—don't render broken UI for empty strings/arrays
+- User-generated content: anticipate short, average, and very long inputs
+
+### Images
+
+- `<img>` needs explicit `width` and `height` (prevents CLS)
+- Below-fold images: `loading="lazy"`
+- Above-fold critical images: `priority` or `fetchpriority="high"`
+
+### Performance
+
+- Large lists (>50 items): virtualize (`virtua`, `content-visibility: auto`)
+- No layout reads in render (`getBoundingClientRect`, `offsetHeight`, `offsetWidth`, `scrollTop`)
+- Batch DOM reads/writes; avoid interleaving
+- Prefer uncontrolled inputs; controlled inputs must be cheap per keystroke
+- Add `<link rel="preconnect">` for CDN/asset domains
+- Critical fonts: `<link rel="preload" as="font">` with `font-display: swap`
+- Prefer `<video autoplay muted loop playsinline>` over animated GIF; provide a still alternative
+- Short non-essential loops: Safari H.264 MP4 `<picture>` source, `prefers-reduced-motion` media condition, and still fallback
+
+### Navigation & State
+
+- URL reflects state—filters, tabs, pagination, expanded panels in query params
+- Links use `<a>`/`<Link>` (Cmd/Ctrl+click, middle-click support)
+- Deep-link all stateful UI (if uses `useState`, consider URL sync via nuqs or similar)
+- Destructive actions need confirmation modal or undo window—never immediate
+
+### Touch & Interaction
+
+- `touch-action: manipulation` (prevents double-tap zoom delay)
+- `-webkit-tap-highlight-color` set intentionally
+- `overscroll-behavior: contain` in modals/drawers/sheets
+- Page rubber-band suppression: `overscroll-behavior: none` on `<html>` inside `@media (pointer: fine)`; keep coarse-pointer page defaults for pull-to-refresh. Test hybrid touch devices: `pointer` describes the primary input, and `none` also disables scroll chaining and native swipe navigation
+- During drag: disable text selection, `inert` on dragged elements
+- Drag/swipe/pinch/path gestures need tap/click and keyboard alternatives unless essential
+- `autoFocus` sparingly—desktop only, single primary input; avoid on mobile
+
+### Safe Areas & Layout
+
+- Full-bleed layouts need `env(safe-area-inset-*)` for notches
+- Avoid unwanted scrollbars: `overflow-x-hidden` on containers, fix content overflow
+- Flex/grid over JS measurement for layout
+
+### Dark Mode & Theming
+
+- `color-scheme: dark` on `<html>` for dark themes (fixes scrollbar, inputs)
+- `<meta name="theme-color">` matches page background
+- Native `<select>`: explicit `background-color` and `color` (Windows dark mode)
+
+### Locale & i18n
+
+- Dates/times: use `Intl.DateTimeFormat` not hardcoded formats
+- Numbers/currency: use `Intl.NumberFormat` not hardcoded formats
+- Detect language via `Accept-Language` / `navigator.languages`, not IP
+- Brand names, code tokens, identifiers: wrap with `translate="no"` to prevent garbled auto-translation
+
+### Hydration Safety
+
+- Inputs with `value` need `onChange` (or use `defaultValue` for uncontrolled)
+- Date/time rendering: guard against hydration mismatch (server vs client)
+- `suppressHydrationWarning` only where truly needed
+
+### Hover & Interactive States
+
+- Buttons/links need `hover:` state (visual feedback)
+- Interactive states increase contrast: hover/active/focus more prominent than rest
+
+### Content & Copy
+
+- Active voice: "Install the CLI" not "The CLI will be installed"
+- Title Case for headings/buttons (Chicago style)
+- Numerals for counts: "8 deployments" not "eight"
+- Specific button labels: "Save API Key" not "Continue"
+- Error messages include fix/next step, not just problem
+- Second person; avoid first person
+- `&` over "and" where space-constrained
+
+### Anti-patterns (flag these)
+
+- `user-scalable=no` or `maximum-scale=1` disabling zoom
+- `onPaste` with `preventDefault`
+- `transition: all`
+- `outline-none` without focus-visible replacement
+- Inline `onClick` navigation without `<a>`
+- `<div>` or `<span>` with click handlers (should be `<button>`)
+- Images without dimensions
+- Large arrays `.map()` without virtualization
+- Form inputs without labels
+- Icon buttons without `aria-label`
+- Hardcoded date/number formats (use `Intl.*`)
+- `autoFocus` without clear justification
+- Animated GIF when compressed video is suitable
+- Gesture-only action without tap/click and keyboard alternative
+
+## Output Format
+
+Group by file. Use `file:line` format (VS Code clickable). Terse findings.
+
+```text
+## src/Button.tsx
+
+src/Button.tsx:42 - icon button missing aria-label
+src/Button.tsx:18 - input lacks label
+src/Button.tsx:55 - animation missing prefers-reduced-motion
+src/Button.tsx:67 - transition: all → list properties
+
+## src/Modal.tsx
+
+src/Modal.tsx:12 - missing overscroll-behavior: contain
+src/Modal.tsx:34 - "..." → "…"
+
+## src/Card.tsx
+
+✓ pass
+```
+
+State issue + location. Skip explanation unless fix non-obvious. No preamble.

package/assets/skills/{design/agemon-design-minimal → essentials/writing-guidelines}/LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2026 Eduardo Calvo
+Copyright (c) 2026 Vercel Labs
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

package/assets/skills/essentials/writing-guidelines/NOTICE.md

@@ -0,0 +1,14 @@
+# Vendored skill
+
+- Source: https://github.com/vercel-labs/writing-guidelines
+- Path in source: command.md
+- Commit: 83e2316b034cf572400513538e4e4da01c4cc742
+- Retrieved: 2026-11-05
+- License: MIT — see `LICENSE` in this directory.
+
+## agemon modifications
+
+- `references/guidelines.md` is upstream's `command.md` with its frontmatter and the `$ARGUMENTS` line removed. The rules and output format are unchanged.
+- `SKILL.md` is agemon's own wrapper. Instead of fetching the guidelines from a URL, it reads `references/guidelines.md`.
+- Judgement call: the wrapper keeps the `name` and the short `description` of the skill agemon installed before, so existing installs are recognised and the skill still routes on the same phrases. That text comes from https://github.com/vercel-labs/agent-skills at commit 063bee94c3f4df8453406c830b0a7df0f2860278 (path `skills/writing-guidelines/SKILL.md`). That repository's README states MIT, but it has no LICENSE file at that commit, so the licence for this carried-over text is stated, not shipped. The rest of the wrapper is written by agemon.
+- Keeps the name `writing-guidelines` rather than an `agemon-*` name, so existing installs are recognised and can be updated.

package/assets/skills/essentials/writing-guidelines/SKILL.md

@@ -0,0 +1,18 @@
+---
+name: writing-guidelines
+description: Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".
+argument-hint: <file-or-pattern>
+---
+
+# Writing Guidelines
+
+Review files for compliance with the Writing Guidelines.
+
+## How it works
+
+1. Read the files the user named, or ask which files or pattern to review.
+2. Read `references/guidelines.md` next to this file. It holds every rule and the output format.
+3. Check each file against all of the rules.
+4. Report findings in the terse `file:line` format the guidelines specify.
+
+The guidelines ship with this skill at a pinned version. Do not look for newer rules elsewhere.

package/assets/skills/essentials/writing-guidelines/references/guidelines.md

@@ -0,0 +1,250 @@
+# Writing Guidelines
+
+Read files, check against rules below. Output concise but comprehensive: sacrifice grammar for brevity. High signal-to-noise.
+
+## Rules
+
+### Planning & content type
+
+- Every page has a plan (overview, goal, audience, content plan, open questions) referenced or linked
+- Content type declared in `meta.contentType`: `Tutorial`, `How-to`, `Reference`, `Conceptual`, `Troubleshooting`, or `Landing`
+- Title is user-shaped (the user's question), not feature-shaped (the engineer's name)
+- Page does one job: tutorial OR how-to OR reference, not three at once
+- Goal is verb-driven (Bloom's taxonomy): "configure", "explain", "debug" (testable)
+- Multi-audience pages: short shared opener, then technical subsections
+
+### Voice & tone
+
+- Active voice. Mental test: append "by monkeys". If the sentence parses, rewrite
+- Direct address: `you`, never `the user` or `one can`
+- Imperative for steps: "Click **Add Project**", not "You will need to click **Add Project**"
+- Sentences under 20 words target
+- Contractions encouraged (`you'll`, `it's`) for warmth
+- Present tense unless describing future behavior
+- Limit `we`: only for deliberate Vercel actions ("we recommend", "we deprecated"), never as a stand-in for "you"
+- No rhetorical questions (sounds like marketing)
+- Second-read test: read each sentence once at speech pace; if you re-read to parse it, name the subject, the action, and the consequence (kill metaphor verbs and pronouns reaching back several sentences)
+
+### Banned words
+
+- `easy`, `simple`, `quick`: puts pressure on the reader and reads as marketing; replace with concrete description ("one command", "default settings", "most projects don't need this")
+- `very`, `just`, `really`: filler; cut or rewrite
+
+### Concision
+
+- Earn every detail: cut a number, name, or implementation detail if a more general phrasing wouldn't change the reader's understanding or action
+- Weasel words: replace vague qualifiers (`significantly`, `many`, `often`, `typically`, `generally`) with a specific number or claim
+- Vague quantifiers: no `near-zero`, `sub-second`, `most requests`; give the figure and cite it (`99.37% of requests see zero cold starts`)
+- Filler/metaphor verbs: name the action instead of reaching for cadence (`moves through`, `lands`, `carries`, `hits` → the literal step)
+
+### AI-generated tells (flag these)
+
+- Summary-style transitions: never open a paragraph by recapping the last one (`With this setup complete…`, `Now that we've explored…`); pivot straight to the next point (`In practice…`, `The catch is…`)
+- Stop-start sentences: don't split one dependent idea into choppy fragments (`Previously this was manual. Now it's automatic. This saves time.` → one sentence); short sentences for emphasis are fine
+- Spec-sheet voice: rewrite sentences that read like a system reading a datasheet (`provides`, `is configurable`, `is explicitly labeled`)
+- Cold-open paragraphs: a body paragraph whose first sentence works as a standalone heading has no antecedent; carry the prior subject forward (`Because…`, `Once…`)
+- Personified artifacts: machines don't perform human-physical actions (`hand the browser a URL` → `the browser fetches the URL`; `the token holds…` → `the token is stored…`)
+- Reused framing: the angle must come from this page, not a template (`The question most teams face is whether…`)
+
+### Tone, by content type
+
+- **Tutorial**: warm, encouraging, predictable structure, no traps
+- **How-to**: terse, direct (reader is mid-task)
+- **Reference**: neutral, exhaustive, quotable
+- **Conceptual**: explain like the reader will teach it back; examples and analogies welcome
+- **Troubleshooting**: empathetic but not apologetic; acknowledge then fix
+
+### Headings
+
+- Sentence case for page headings (`H1` `H2` `H3`): "Configure environment variables", not "Configure Environment Variables"
+- Title case for nav labels: "Configuring Environment Variables"
+- `meta.title` becomes the `H1`; `meta.navLabel` becomes the sidebar entry
+- Subheadings descriptive, not cute: "Caveats when self-hosting on Cloudflare", not "Caveats"
+- Reader should be able to guess section content from the heading alone
+
+### Structure
+
+- Every page opens with a one-paragraph TL;DR of what the page covers
+- Every major section opens with a summary sentence
+- Acronyms spelled out on first use: "Content Security Policy (CSP) blocks inline scripts"
+- Define every term the first time you use it (link to its conceptual page)
+- Reference docs organized by surface; education docs organized by reader task
+- Keep paragraphs to 2 to 4 sentences; split anything longer or covering two ideas
+
+### Lists
+
+- Three or more list-shaped items in a paragraph: convert to a list
+- Bulleted for unordered; numbered for ordered (lifecycles, sequential steps)
+- Always introduce a list with a colon
+- No periods at the end of list items unless they are full sentences
+- Bold/description format: `- **Term**: description here` (colon after bold term)
+
+### Code
+
+- Code blocks need a language tag for syntax highlighting
+- TypeScript is the default for new code unless the surface is genuinely language-agnostic
+- Multi-step flows wrapped in `<Steps/>` so structure is visible
+- Highlight load-bearing lines: `` ```typescript {8-12,23-37} ``
+- ≤80 columns per line in snippets
+- ≤25 lines per snippet; split longer blocks with prose
+- Omit defaults; don't repeat variable definitions, use shared var
+- Minimal comments in code blocks; prefer prose explanation
+- Explain what every code block does in prose (don't drop and run)
+- Don't reference full example files at the end of guides ("See `train.py`"); the guide is the deliverable
+
+### Placeholders
+
+- Text placeholders: `snake_case`, descriptive: `your_access_token_here` (so reader can double-click to select before pasting)
+- Number placeholders: count up `1234567890123` (recognizable as fake, predictable)
+- Never `<TOKEN>`, `xxx`, `your-token`, or generic ALL_CAPS
+
+### Data sizes & units
+
+- Space + uppercase unit: `64 KB`, `5 KB`, `200 ms`
+- Exception: seconds is bare: `30s`
+- Consistent across the corpus so readers can develop scanning habits
+
+### Money & pricing pages
+
+- Uncompromising detail: err on "too much"
+- Use tables for pricing
+- Never assume reader knows the pricing model or whether their workload counts as one invocation or several
+- Clarity and transparency above all else
+
+### Emphasis
+
+- **Bold** means UI element or critical fact, never emphasis-for-emphasis-sake
+- Reaching for bold for tone: the sentence is weak; rewrite it
+- `Inline code` for paths, file extensions, identifiers, short snippets: `/api`, `.tsx`, `body`, `query`, `req`
+- Rule: if it would look weird without a monospace font, monospace it
+
+### Punctuation & typography
+
+- Never em dashes (`—`) or dashes (`-`) as punctuation; use colons, commas, periods, or rephrase
+- Curly quotes `"` `"` and `'` `'`, not straight `"` or `'`
+- Ellipsis `…`, not three dots `...`
+- Loading states end with `…`: `Loading…`, `Saving…`
+- Non-breaking spaces in `10&nbsp;MB`, `⌘&nbsp;K`, brand names
+- `&` over "and" only where space-constrained (nav labels, buttons)
+
+### Source formatting
+
+- Don't hard-wrap paragraphs: each paragraph is one line in source, let the editor wrap
+- One blank line before headings; one blank line before and after code blocks
+- No `---` horizontal rules between sections
+- No extra blank lines between elements that aren't paragraph breaks
+
+### Links
+
+- Define every term the first time it appears, link to its conceptual page
+- Anchor text names the destination; never bare URLs or `here`/`link`
+- Dashboard deep links use the standard format: `https://vercel.com/d?to=%2F%5Bteam%5D%2F~%2Fai-gateway%2Fapi-keys&title=AI+Gateway+API+Keys`
+- Link to canonical product docs where relevant: `https://vercel.com/docs/vercel-sandbox`, `https://vercel.com/docs/ai-gateway`
+- AI Gateway model catalog: `https://vercel.com/ai-gateway/models`
+
+### Models in examples
+
+- Always use the latest model strings: `anthropic/claude-opus-4-7`, not `anthropic/claude-sonnet-4` or older
+- For image generation default: `google/gemini-3.1-flash-image-preview`
+
+### AI workflow
+
+- You are accountable for the content you produce, however it is created
+- You are the final arbiter; the model proposes, you dispose
+- Hold technical accuracy to a high standard: docs are also consumed by LLMs, wrong docs train wrong models
+- Use only enterprise models that do not train on your data (especially for unreleased products)
+- Disclose AI use in the PR (model + prompts if useful)
+- Plan first by hand; the plan is the spec the model works against
+- Use plan-mode in your editor (Cursor, Claude) before letting the model write
+- Tell the model to follow `AGENTS.md` and the linting checklist
+- Run a test prompt against the preview: "given this plan's goal, can the model complete the task using only this page?"
+- Final human review always
+
+### Quality checklist (required boxes are non-negotiable)
+
+- **Findability**: sidebar bucket set via `meta.category`; UI links to docs from any dashboard surface that exposes the feature
+- **Accuracy**: code samples actually run; screenshots map 1:1 to current UI and use the ACME demo account
+- **Relevance**: code samples included where applicable (TypeScript first; `<Steps/>` for multi-step flows)
+- **Clarity**: overview addresses who/what/where/why; high-level use cases laid out; quickstart for new products; prerequisites listed on tutorials; sample repo in `vercel/examples` for multi-step tutorials; steps detailed not vague; visual aids in confusing sections; simplest path recommended when multiple exist
+- **Completeness**: limits documented; all-limits tables updated; content plan followed and goals addressed
+- **Readability**: nav names scannable and use action verbs; content types accurately used; subheadings descriptive; topics start with summaries; code blocks formatted correctly; active voice where warranted
+
+### Review
+
+- PR description links to the content plan, lists what to review, and links the preview URL
+- Ping the team via the PR link (not the plan or preview directly)
+- Author is accountable, not the reviewer; reviewers are liberal with approvals
+- Suggestion comments for small text fixes; preview comments for anything bigger
+- Disagreement is fine; reject with a one-line reason and move on
+
+### Anti-patterns (flag these)
+
+- Em dashes (`—`) or dashes (`-`) used as punctuation
+- `easy`, `simple`, `quick` describing reader actions
+- Passive voice (apply "by monkeys" test)
+- Title Case in page headings (only sentence case in `H1` through `H6`)
+- Generic placeholders: `<TOKEN>`, `xxx`, `your-token`, `ABC123`
+- Code blocks without a language tag
+- JS examples where TypeScript is the convention
+- Code blocks over 25 lines without prose between
+- Hard-wrapped prose paragraphs (multiple lines for one paragraph in source)
+- `---` horizontal rules between sections
+- Subheadings that are single generic words: `Overview`, `Caveats`, `Notes`
+- Bold used for emphasis instead of UI element or critical fact
+- Page or section without an opening summary
+- Straight quotes (`"`, `'`) instead of curly (`"`, `'`)
+- Three dots (`...`) instead of ellipsis (`…`)
+- Acronyms used before being spelled out
+- Bare unit numbers (`64KB`, `5kb`, `200MS`) instead of `64 KB`, `5 KB`, `200 ms`
+- "We" standing in for "you"
+- Rhetorical questions
+- Filler words: `very`, `just`, `really`, `simply`
+- References to "the full example file at the end of the guide" rather than inlining the code
+- Outdated model strings in examples (`anthropic/claude-sonnet-4`, `gpt-4o`, DALL-E)
+- Hardcoded date/number formats instead of `Intl.DateTimeFormat` / `Intl.NumberFormat` in code samples
+- "Loading..." instead of "Loading…"
+- Summary-style transitions recapping the previous paragraph (`With this setup complete…`)
+- Stop-start fragments splitting one dependent idea into choppy sentences
+- Spec-sheet voice reading like a datasheet (`provides`, `is configurable`, `is explicitly labeled`)
+- Cold-open body paragraphs whose first sentence has no antecedent
+- Personified artifacts performing human-physical actions (`hand the browser a URL`)
+- Reused/template framing not specific to the page (`The question most teams face is whether…`)
+- Weasel words instead of a specific claim (`significantly`, `many`, `often`, `typically`, `generally`)
+- Vague quantifiers without a cited figure (`near-zero`, `sub-second`, `most requests`)
+- Filler/metaphor verbs instead of the literal step (`moves through`, `lands`, `carries`, `hits`)
+- Sentences that need a second read to parse
+- Paragraphs over 4 sentences or covering two ideas
+- Bare URLs or `here`/`link` as anchor text
+
+## Output Format
+
+Group by file. Use `file:line` format (VS Code clickable). Terse findings.
+
+```text
+## content/docs/sandbox.mdx
+
+content/docs/sandbox.mdx:1 - missing meta.contentType
+content/docs/sandbox.mdx:12 - title "Vercel Sandbox" is feature-shaped, not user-question
+content/docs/sandbox.mdx:24 - passive voice ("the sandbox is created...")
+content/docs/sandbox.mdx:31 - banned word "easy"
+content/docs/sandbox.mdx:47 - "..." → "…"
+content/docs/sandbox.mdx:58 - code block missing language tag
+content/docs/sandbox.mdx:71 - placeholder <TOKEN> → your_access_token_here
+content/docs/sandbox.mdx:89 - "64KB" → "64 KB"
+content/docs/sandbox.mdx:102 - H2 "Caveats" too generic; add specificity
+content/docs/sandbox.mdx:118 - em dash in prose, replace with colon/comma
+
+## content/docs/ai-gateway.mdx
+
+content/docs/ai-gateway.mdx:5 - title case in H1; sentence case only
+content/docs/ai-gateway.mdx:18 - acronym AI Gateway used before being spelled out
+content/docs/ai-gateway.mdx:34 - bold for emphasis, not UI element
+content/docs/ai-gateway.mdx:52 - `anthropic/claude-sonnet-4` outdated; use `anthropic/claude-opus-4-7`
+content/docs/ai-gateway.mdx:71 - hard-wrapped paragraph (lines 71-74)
+
+## content/docs/cron.mdx
+
+✓ pass
+```
+
+State issue + location. Skip explanation unless fix is non-obvious. No preamble.

package/assets/skills/founder/agemon-founder-board/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Jake Schincariol
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/assets/skills/founder/agemon-founder-board/NOTICE.md

@@ -0,0 +1,11 @@
+# Vendored skill
+
+- Source: https://github.com/Jakeschincariol/founder-skill
+- Path in source: skills/founder-board
+- Commit: fd9385b0cfe1b96bebce3898fbd506d73eff5a9d
+- Retrieved: 2026-11-05
+- License: MIT — see `LICENSE` in this directory.
+
+## agemon modifications
+
+- Renamed from `founder-board` to `agemon-founder-board`, and updated every reference to the pack's other skills to their new names, in the Markdown and in the scripts.

package/assets/skills/founder/agemon-founder-board/SKILL.md

@@ -0,0 +1,111 @@
+---
+name: agemon-founder-board
+description: >-
+  Your board of directors. Puts a business idea in front of a three-member board,
+  each a sub-agent reading the idea through one published framework: the Offers
+  lens (from Alex Hormozi's $100M Offers), the Monopoly lens (from Peter Thiel's
+  Zero to One) and the Product lens (from Walter Isaacson's biography of Steve
+  Jobs). Each member scores the idea, names the risks that would kill it and votes
+  fund, fund with conditions, or pass. Use when the user says "test my business
+  idea", "would this work", "pressure-test this", "what would a board say", "is
+  this a good business", or starts the founder pack on a new idea.
+argument-hint: "<the business idea, or leave blank to use the conversation>"
+---
+
+# agemon-founder-board
+
+The first meeting. Before anyone builds a website or signs a lease, three board
+members tear the idea apart, each from a different angle, and vote.
+
+What the user typed after `/agemon-founder-board`: `$ARGUMENTS`. If that is blank, take
+the idea from the conversation.
+
+## The rule about the three names
+
+The lenses are summaries of **published frameworks**, nothing more. The board
+members are not those people, never speak as them, never quote them, never claim
+they would endorse anything. Write "the Offers lens", never "Alex Hormozi says".
+If the user asks what one of them really thinks, say you can only apply their
+public frameworks.
+
+## Step 0: the idea file
+
+Everything in the founder pack reads `founder/idea.md` in the user's project. If
+it does not exist, write it now from the conversation:
+
+```markdown
+# <business name, or a working name>
+
+- What it is: one sentence.
+- Who it is for: the target customer, as specific as the user can make it.
+- What it sells, at what price: the core product and its price.
+- Where and how: city or online, how customers find it, how it is delivered.
+- Budget and constraints: money, time, skills, anything already decided.
+```
+
+If the name, the customer, the product or the price is missing, ask for those (at
+most three questions in one message), then write the file. Do not invent a
+budget, a market size or a competitor.
+
+## Step 1: brief the board
+
+Write `founder/board/brief.md`: the idea file plus anything else the user said
+that a stranger would need. **Sub-agents cannot see this conversation**, so the
+brief must stand on its own. Do not add your own opinion of the idea to it.
+
+## Step 2: convene
+
+Launch three sub-agents in ONE message (Agent tool, `subagent_type:
+general-purpose`, one per member), each told: `Read founder/board/brief.md and
+agemon-founder-board's lenses.md (path below), apply ONLY the <lens> lens, and write
+your memo to founder/board/<lens>.md.` The lens file is `lenses.md` in this
+skill's folder (`${CLAUDE_SKILL_DIR}/lenses.md`; if that path is not expanded,
+use the base directory Claude Code printed for this skill).
+
+Each memo, in this shape:
+
+```markdown
+# <Lens> lens
+Score: <1-10> | Vote: FUND / FUND IF / PASS
+## What is strong
+## What would kill it (the top 3, most dangerous first)
+## The questions I would ask the founder
+## If FUND IF: the conditions
+```
+
+## Step 3: the chair's summary
+
+Read the three memos (they are short) and write `founder/board.md`:
+
+1. The vote, e.g. "2 fund if, 1 pass", and the average score.
+2. The risks more than one member raised: these go first.
+3. Every condition, merged, as a checklist the rest of the pack can tick off
+   (the CFO, the consumer panel and pricing will test most of them).
+4. One paragraph: the strongest version of this business the board can see.
+   It may differ from what the user pitched; say so plainly.
+
+Keep the members' disagreements. A board that agrees on everything was not doing
+its job.
+
+## Rules
+
+- Score the business, not the founder.
+- No made-up facts. If a lens needs a number nobody has yet (market size, cost of
+  acquiring a customer), name it as an open question and say which skill answers
+  it (`/agemon-founder-competitors`, `/agemon-founder-consumer`, `/agemon-founder-cfo`).
+- A PASS is a result, not a failure. Say it plainly.
+
+## Output
+
+`founder/idea.md`, `founder/board/` (brief and three memos), `founder/board.md`.
+Then say the vote in one line and suggest the next step: `/agemon-founder-competitors`
+to see who is already there, or `/agemon-founder-consumer` to put it in front of 100
+simulated buyers.
+
+## Where the pack goes next
+
+```
+board -> competitors -> consumer -> pricing -> offer -> cfo -> marketing -> brand -> ops -> launch -> plan
+```
+
+Every skill can also run on its own; each reads whatever is already in `founder/`.