@simpleapps-com/augur-skills 2026.3.15 → 2026.3.17

package/package.json

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

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

@@ -16,12 +16,15 @@ All projects live under `~/projects/` in two groups:
 ~/projects/
 ├── simpleapps/          # Internal repos (augur-*, shared infra)
 │   └── <repo-name>/
-└── clients/             # Client site repos
-    └── <site-name>/
+├── clients/             # Client site repos
+│   └── <site-name>/
+└── workspaces/          # VSCode/Cursor workspace files
+    └── <project-name>.code-workspace
 ```
 
 - Internal repos go in `~/projects/simpleapps/`
 - Client site repos go in `~/projects/clients/`
+- Workspace files go in `~/projects/workspaces/` — one `.code-workspace` per project
 
 ## Project Directory Layout
 
@@ -36,7 +39,7 @@ Every project MUST use this layout:
 ├── wiki/               # Wiki repo (simpleapps-com/<name>.wiki.git)
 ├── wip/                # Work-in-progress files (not in git)
 ├── tmp/                # Temporary files (not in git)
-└── .simpleapps/        # Credentials (not in git)
+└── .simpleapps/        # Config, credentials, site profile (not in git)
 ```
 
 The parent `{project}/` is NOT a git repo — it keeps code and wiki side-by-side. The git repo is always at `repo/`. Use `git -C repo` for git operations from the project root.
@@ -49,17 +52,70 @@ The parent `{project}/` is NOT a git repo — it keeps code and wiki side-by-sid
 | Repo `.claude/CLAUDE.md` | `repo/` | Quick reference + wiki links |
 | Active task context | `wip/` | `{issue-number}-{short-desc}.md` files |
 | Temporary files | `tmp/` | Throwaway files, scratch space, build artifacts |
-| Project secrets | `{project}/.simpleapps/` | Site-specific credentials |
-| Global secrets | `~/.simpleapps/` | Shared credentials across all projects |
+| SimpleApps config | `.simpleapps/` | Settings, site profile, credentials (see below) |
 
 **WIP**: Research, plans, decisions, test results. MUST NOT contain secrets, final docs, or code.
 
-**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.
 
+## .simpleapps/ Configuration
+
+Two scopes, project overrides user:
+
+```
+~/.simpleapps/                    # User global
+├── settings.json                 # Config (projectRoot, orgName)
+├── basecamp.json                 # Basecamp MCP credentials
+└── augur-api.json                # Augur API MCP credentials
+
+{project}/.simpleapps/            # Project (gitignored)
+├── settings.json                 # Project config overrides
+├── site.json                     # Site profile (defaults, PII, auth)
+├── basecamp.json                 # Project basecamp overrides (if needed)
+└── augur-api.json                # Project augur-api overrides (if needed)
+```
+
+### File types
+
+| File | Scope | Purpose | Read by |
+|------|-------|---------|---------|
+| `settings.json` | Global + project | Infrastructure config | All skills via project-defaults |
+| `site.json` | Project only | Site profile — defaults, search terms, PII, auth | Skills needing site context |
+| `basecamp.json` | Global + project | Basecamp MCP credentials | Basecamp MCP server |
+| `augur-api.json` | Global + project | Augur API MCP credentials | Augur API MCP server |
+
+### settings.json
+
+```json
+{
+  "projectRoot": "~/projects"
+}
+```
+
+Resolution: read `{project}/.simpleapps/settings.json` first, fall back to `~/.simpleapps/settings.json`, fall back to defaults. Field-level override — project wins for any field it defines.
+
+### site.json
+
+One per client project. Consistent structure across all sites — same fields, different values. Replaces the old `{siteId}.json` pattern.
+
+```json
+{
+  "siteId": "...",
+  "siteName": "...",
+  "auth": { },
+  "defaults": { }
+}
+```
+
+### Rules
+
+- MUST NOT commit `.simpleapps/` to git — contains PII and credentials
+- MUST NOT save site data to wiki or memory — PII
+- MUST NOT create `{siteId}.json` files — use `site.json` instead
+- If old `{siteId}.json` files exist, `/project-init` will flag them for migration to `site.json`
+
 ## 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/wiki/SKILL.md

@@ -105,6 +105,31 @@ All projects follow the same directory layout (see `simpleapps:project-defaults`
 
 MUST NOT use `find`, `grep`, `cat`, `ls`, or any shell command to explore other projects. The paths are known — use the dedicated tools directly.
 
+### Search all wikis
+
+Every wiki on the machine is a local knowledge base. When looking for how something was solved, search across ALL wikis — not just the current project:
+
+1. Read `~/.simpleapps/settings.json` to get `projectRoot`
+2. Pull the latest for all wikis before searching:
+   - `git -C {projectRoot}/clients/*/wiki pull` (one call per wiki, not a glob)
+   - `git -C {projectRoot}/simpleapps/*/wiki pull`
+3. Search across all wikis with Grep:
+   - `Grep(pattern: "...", path: "{projectRoot}/clients", glob: "*/wiki/*.md")`
+   - `Grep(pattern: "...", path: "{projectRoot}/simpleapps", glob: "*/wiki/*.md")`
+4. Read the matching pages to get the full context
+
+Use Glob to discover which projects have wikis: `Glob(pattern: "{projectRoot}/clients/*/wiki")` and `Glob(pattern: "{projectRoot}/simpleapps/*/wiki")`.
+
+The wikis are kept fresh by `/curate-wiki` runs across projects. Searching locally is instant and requires no internet access — the knowledge is already on the machine.
+
+**What to search for:** testing patterns and checklists, architecture decisions, coding conventions, deployment procedures, and how specific features were implemented. Other sites have already solved many of the same problems — search before building from scratch.
+
+## Testing Page
+
+Every project wiki SHOULD have a `Testing.md` page. This is the E2E verification checklist that `/verify` uses to walk through the site in Chrome. The page grows over time — `/curate-wiki` SHOULD add testing knowledge learned during the session (new edge cases, failure patterns, test data) to the Testing page.
+
+A good Testing page covers: test tiers (automated vs manual), test data (items, accounts, cards), and an E2E checklist organized by page area (homepage, listing, detail, cart, checkout, etc.). Each checklist item is a concrete, verifiable condition — not vague ("works") but specific ("price shows $9.26").
+
 ## Keep It Lean
 
 - Document patterns and principles, not exhaustive lists

package/skills/simpleapps/workflow/SKILL.md

@@ -64,6 +64,29 @@ gh issue create --repo simpleapps-com/<repo> \
 - Include the Basecamp todo URL in the GitHub issue body (under a `## Basecamp` heading)
 - After creating the issue, provide the GitHub issue URL to the user so they can add it to the Basecamp todo comments
 
+## Development Lifecycle
+
+The full workflow from task to delivery, each step feeding the next:
+
+```
+/triage → /wip → /investigate → /discuss → /implement → /quality → /verify → /curate-wiki
+```
+
+| Phase | Command | What happens |
+|-------|---------|-------------|
+| Pick work | `/triage` | See open PRs and unlinked issues |
+| Scaffold | `/wip` | Create a WIP file from Basecamp or GitHub issue |
+| Research | `/investigate` | Explore codebase, update WIP with findings |
+| Align | `/discuss` | Conversational alignment before acting |
+| Build | `/implement` | Execute the plan — code changes only, no commits |
+| Code checks | `/quality` | Lint, typecheck, test, package freshness |
+| Browser checks | `/verify` | Walk through wiki's Testing.md checklist in Chrome |
+| Capture | `/curate-wiki` | Update wiki with session learnings, audit CLAUDE.md/rules |
+
+**Key principle:** each session generates knowledge. `/curate-wiki` captures it — including new testing patterns, edge cases, and failure modes discovered during `/implement` and `/verify`. This grows the wiki's Testing.md page over time, making future `/verify` runs more thorough. This is the learning organization in action.
+
+Commands like `/research` and `/discuss` can be used at any stage. `/quality`, `/verify`, `/curate-wiki`, and `/wiki-audit` can run independently.
+
 ## References
 
 - See `simpleapps:basecamp` skill for MCP tools, Chrome fallback, and Basecamp navigation