From simpleapps
Project deployment conventions — reads the wiki Deployment page and executes submit, deploy, or publish steps. Refuses to operate without a Deployment page.
npx claudepluginhub simpleapps-com/augur-skills --plugin simpleappsThis skill is limited to using the following tools:
First, use Skill("git-safety") to load git guardrails.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
First, use Skill("git-safety") to load git guardrails.
This skill reads the project's wiki/Deployment.md and executes the steps defined there. Each project defines its own deployment workflow — this skill is the executor, the wiki is the config.
Every project wiki MUST have a Deployment.md page with up to three sections:
## Submit
How to commit and create a PR for review.
## Deploy
How to deploy to staging.
## Publish
How to release to production.
Not all projects need all three. Client sites may only have Submit and Deploy. Package repos may have all three.
wiki/Deployment.md/curate-wiki to generate itThe user invoking a command IS the approval to execute all its steps, including git writes. Do not stop to ask for confirmation mid-execution.
/submit — execute all steps (commit, push, PR). Report at the end./deploy — execute all steps. Report at the end./publish — EXCEPTION: must complete the verification gate below and get secondary confirmation BEFORE executing any publish steps. This is the only command that pauses for approval.wiki/Deployment.md does not exist, STOP IMMEDIATELY. Do not guess, do not improvise, do not infer steps from the codebase. Tell the user to run /curate-wiki to generate it. Then do nothing else.Before executing any Publish steps, MUST:
git log from last tag)gh run list or local test run)This is not just git-safety. It is an active verification checklist — the user MUST see exactly what they are releasing and confirm that specific version.