diff --git a/.claude/skills/products/business-site/SKILL.md b/.claude/skills/products/business-site/SKILL.md index 7ecda9ece..b416260bc 100644 --- a/.claude/skills/products/business-site/SKILL.md +++ b/.claude/skills/products/business-site/SKILL.md @@ -37,6 +37,7 @@ material refreshes. Validate with the Node 24 root application build before any - **D. Content Sync** (don't `git submodule update --remote`): public EN/DA descriptions live in `src/data/public-products.json`, the unified Projects page's rendered source. Update the `public-products:` inventory in `src/content/docs/projects/active.mdx` and run `scripts/refresh-public-stars.sh` when the catalogue set changes; that MDX file holds legacy portfolio metadata, not public descriptions. Keep KSail **brief + linked to ksail.devantler.tech — never duplicate its docs**. Shared automation is `.github`; the separate `actions` card is explicitly legacy. Templates retain supporting pages under `src/content/docs/templates/`. Internal deployments do not enter the public catalogue. **Never modify blog posts during Content Sync** — blog changes use task G with their own evidence/editorial review. Validate the drift guard and actual production catalogue → draft `docs: sync project descriptions`. - **E. Content Review (Mondays only;** rotate unbloat ↔ editorial in `content_review`): **Unbloat** one not-recently-cleaned file (skip frontmatter `disable-agentic-editing: true`), cut duplication/verbosity ≥20% w/o losing accuracy. **Editorial** rotate lens weekly (Technical Rigor → Clarity → Onboarding → Portfolio Balance). - **F. Repo Assist:** triage/label new issues + PRs; comment on the oldest open item lacking an AI comment (1–3/run); self-spotted fixes → draft PR (use `Fixes #N` when it closes an issue); ≤3 stale-PR/issue nudges. +- **H. Add-on candidates (monthly):** list open `addon-candidate` issues in business-site (`gh issue list --repo devantler-tech/business-site --label addon-candidate`). Each describes one kind of request from outside the offer, never the customer, and counts how often it was asked. When one reaches 3 requests, propose it to the maintainer as a standard add-on with a fixed VAT-inclusive price, through a maintainer channel. Record `last_addon_review` in memory. - **G. Blog Stewardship (low priority; monthly evidence review, worthwhile publish/refresh every 4–8 weeks):** complete a topic/evidence audit across portfolio balance, recurring questions/issues, shipped outcomes, and stale claims before advancing `last_blog_review`. Inspect privacy-safe aggregate Umami,