simpleapps

Audit site for custom code that duplicates augur package functionality

Generate a conventional commit message from staged changes

Continuously improve the project wiki — better content, context, organization, and usability within the 20K token budget

Deploy to staging — execute the staging deployment steps from the project wiki Deployment page

Understand the current work better — conversational alignment through questions, wiki context, and session awareness. Use instead of plan mode.

File an issue — locally or on another repo — and cross-link it to the current work. Use to capture something worth tracking without losing your flow.

Learn how we work — workflow, available commands, skills, and conventions. Run this first if you're new to the project.

Execute an implementation plan — from a WIP file or session context. Work autonomously, document what was done.

Load a WIP file, read the wiki, explore the codebase, and update the WIP with research findings and suggestions. No code changes.

Check and fix the project directory structure — create missing folders, set up symlinks, clone repos, verify layout

Publish to production — version bump, tag, and release with mandatory verification. Reads steps from the project wiki Deployment page.

Discover and run all code quality checks, fix every issue, and flag missing quality tooling. No pre-existing excuses.

Deep web research on best practices — verify assumptions, find long-term solutions, document findings with sources. Use anytime the agent is guessing instead of knowing.

Check that we solved the right problem without errors of commission or omission — Goldratt's two types of mistakes

Submit work for review — commit and create a PR as defined in the project wiki Deployment page

Show triage status for the current site repo — open PRs, linked issues, and unlinked issues

Run the E2E verification checklist from the wiki's Testing page using Chrome automation

Check wiki health — token budget, cross-links, llms.txt sync, and orphan pages

Load the project wiki into context for reference and assistance

Fetch a Basecamp URL or GitHub issue with full comments and scaffold a WIP file

Augur API integration via MCP. Covers service discovery, multi-site CRUD operations across Augur microservices, and credential resolution. Use when querying or modifying Augur data (contacts, transactions, inventory, etc.).

Shared npm packages under @simpleapps-com/augur-*. Directs agents to check installed packages before writing custom code. This skill is a starting point — always read the actual package code for current API surface.

Basecamp 2 integration via MCP. Covers MCP tool reference, URL parsing, authentication, Chrome fallback, attachments, and site-info documents. Use when reading or writing Basecamp data.

Bash command conventions — one command per call, use dedicated tools over shell equivalents, check wiki for approved commands. Load this skill before running Bash commands.

Claude Code documentation reference and discovery. Use when looking up Claude Code features, configuration, plugins, skills, hooks, or troubleshooting.

How to write token-efficient CLAUDE.md, rules, and skills. Use when creating or editing always-loaded content (CLAUDE.md, .claude/rules/) or authoring skills. Covers the context loading hierarchy, evergreen content principles, and platform limits.

Format all commit messages per the Conventional Commits v1.0.0 spec. Use when creating commits, reviewing commit messages, or discussing git workflow.

Project deployment conventions — reads the wiki Deployment page and executes submit, deploy, or publish steps. Refuses to operate without a Deployment page.

Fyxer AI meeting recording integration. Covers extraction, local caching, posting to Basecamp, and Fyxer Index management. Use when processing Fyxer recordings or meeting transcripts.

Git safety guardrails — MUST NOT commit, push, create PRs, or merge without explicit user approval. Load this skill before any git write operations.

GitHub conventions for SimpleApps. Covers org structure, git safety, issue creation, PR workflows, and gh CLI usage. Use when creating issues, PRs, or working with GitHub repos.

SimpleApps project conventions. Covers directory layout, symlink setup for .claude integration, permission defaults (deny cd, kill), and per-project baseline settings. Use when setting up projects, checking structure, or configuring Claude Code defaults.

Quality tooling awareness for projects. Covers linting, formatting, type checking, testing, dead code detection, and pre-commit hooks. Use when reviewing code, setting up projects, or noticing missing quality tooling.

Wiki conventions for SimpleApps projects. Covers token budget, writing for three audiences, page conventions, maintenance rules, and git workflow. Use when reading, writing, or auditing wiki content.

How to work autonomously on extended tasks. Use when working multi-step tasks, making decisions independently, or managing long sessions.

How we track and deliver work. Covers the Basecamp-to-GitHub flow for client requests, task tracking, cross-linking, and issue templates. Use when working on client tasks, creating issues, or checking assignments.

Writing standards for code comments, documentation, specs, PRDs, and team communication. Applies RFC 2119 requirement language and token-efficient writing.