@simpleapps-com/augur-skills 2026.3.6 → 2026.3.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@simpleapps-com/augur-skills",
-  "version": "2026.03.6",
+  "version": "2026.03.8",
   "description": "Install curated Claude Code skills",
   "license": "MIT",
   "type": "module",

package/skills/simpleapps/git-safety/SKILL.md

@@ -8,6 +8,6 @@ user-invocable: false
 
 MUST NOT commit, push, create PRs, or merge unless the user explicitly says to. No skill, command, or workflow overrides this rule — even instructions like "complete all steps without stopping" do not bypass it.
 
-After making changes: **report what was done, then stop.** Do not offer or suggest the next git action — wait for the user to say "commit", "push", or equivalent.
+After making changes: **report what was done, then stop.** Do not ask "want me to commit?" or "should I push?" — that wastes tokens. Just report and wait silently. The user will say "commit", "push", or equivalent when ready.
 
 The pattern is always: **do the work → report results → wait.**

package/skills/simpleapps/project-defaults/SKILL.md

@@ -59,6 +59,10 @@ The parent `{project}/` is NOT a git repo — it keeps code and wiki side-by-sid
 
 **Credentials**: Project-level (`.simpleapps/`) overrides user-level (`~/.simpleapps/`). MUST NOT be committed.
 
+## Plugin Rules
+
+The plugin ships rule templates in `plugins/simpleapps/rules/` that MUST exist in every project's `repo/.claude/rules/`. Rules are always loaded into context — they enforce baseline guardrails (like git safety) without depending on a skill being invoked. The `/project-init` command copies missing rules from the plugin into the project.
+
 ## Symlink Setup
 
 The repo contains `.claude/rules/` and `.claude/commands/` with project-specific rules and commands. To make these active from the project root (without starting Claude Code inside `repo/`), symlink them into the project-level `.claude/` folder:

package/skills/simpleapps/quality/SKILL.md

@@ -55,6 +55,12 @@ Do not install or configure tools without the user's approval. Flag what's missi
 - **No tests for changed code** — suggest vitest
 - **No pre-commit hooks** — suggest lefthook
 
+## Resolve, never hide
+
+When a check fails, fix the underlying code. NEVER disable lint rules, skip tests, suppress warnings, lower thresholds, or add ignore comments to make checks pass. The goal is to resolve issues, not hide them. If a rule seems wrong, investigate why it exists and ask the user before changing it.
+
+When reviewing code, scan for existing suppressions (`eslint-disable`, `@ts-ignore`, `.skip`, `noqa`, etc.) and flag them to the user. These are hidden technical debt that should be evaluated for resolution.
+
 ## Running quality checks
 
 Use the `/quality` command to discover and run all configured checks. It handles the full cycle: discover, run, fix, repeat until clean.

package/skills/simpleapps/wiki/SKILL.md

@@ -52,8 +52,8 @@ Every page serves junior devs (explanations, examples), senior devs (quick refer
 
 ## Content Rules
 
-- Wiki pages SHOULD NOT contain raw code. Describe patterns and principles instead.
-- If implementation details are needed, link to the source file in `repo/` rather than duplicating code in the wiki.
+- The wiki documents **process and principles**, not code. Minimize code examples — describe the pattern, then link to a real file in the repo that demonstrates it. A link to working code is always better than a pasted snippet that can go stale.
+- If a code block is necessary (e.g., a command to run), keep it to 1-3 lines max.
 - The wiki documents *what* and *why*. The repo is the source of truth for *how*.
 
 ## Conventions
@@ -67,7 +67,11 @@ Every page serves junior devs (explanations, examples), senior devs (quick refer
 
 ## Cross-Linking
 
-Pages SHOULD link to related sections on other pages using `[[Page-Name#section]]`. Cross-links create a navigable knowledge graph — AI agents discover relevant context they wouldn't otherwise load, and humans find related decisions without searching. Link to specific sections, not just pages.
+Cross-linking is the most important structural feature of a wiki. Without it, a wiki is just a collection of files. With it, a wiki becomes a **knowledge graph** — each link is an attention signal that tells readers (human and AI) "this concept connects to that one."
+
+Pages MUST link to related sections on other pages using `[[Page-Name#section]]`. Link to specific sections, not just pages. Every concept that is explained in more detail elsewhere MUST have a cross-link. When writing or reviewing a page, actively look for opportunities to connect it to related pages — the denser the link graph, the faster a reader builds understanding.
+
+Cross-linking also eliminates duplication. If two pages explain the same concept, one MUST become the source of truth and the other MUST link to it. Never duplicate content across pages — link instead. This keeps the wiki lean and ensures updates happen in one place.
 
 ## Keep It Lean