Loading...
Loading...
Found 185 Skills
(NS) Generate and adapt .gitlab-ci.yml for SaaS products with backend and frontend — test, build, E2E gate, deploy by branch. Use when the user asks for GitLab CI, pipeline setup, or CI/CD bootstrap for a monorepo product. Uses references/templates/gitlab-ci.template.yml as baseline. Out of scope for pure agent-runtime repos without backend+frontend layout.
Marketing playbook for bootstrapped startups with zero budget. Covers organic-only channels including SEO, community building, social media, and word-of-mouth tactics that cost nothing but time. Follow @WeiYipei on X.
Harness patterns for coding agents — memory, permissions, context engineering, delegation, skills, hooks, bootstrap.
Commit SpecStory transcripts and Claude/Cursor/OpenCode/Codex plans with feature diffs, derive staged `AI-Assisted-By` plus transcript/plan trailers, prevent secret leaks, and ignore SpecStory machine-local state. Use when asked to commit/save/stage agent sessions, record cross-harness provenance, bootstrap pre-commit, fix `.specstory/statistics.json` churn, scrub a transcript, or remediate accidental secret commits/pushes with rotate-first discipline.
Project documentation lifecycle for PHP/Laravel and Node/TypeScript/React projects — bootstrapping essential docs, naming and folder conventions, freshness, and cleanup of AI-generated junk and stale files. Use when starting a new project, setting up docs/ structure, auditing markdown files, cleaning up the docs folder, or deciding which docs to keep, archive, or delete. Triggers on "set up docs", "audit docs", "clean up markdown", "what docs does this project need", "organize docs folder", "find stale docs".
When you want multiple expert perspectives on a founder/operator question — a simulated personal board of advisors staffed by legendary founders, CEOs, and operators (Jason Fried, Elon Musk, Jeff Bezos, Jensen Huang, Bob Iger, Paul Graham, Naval Ravikant, Sara Blakely). Bring a real decision — "should I raise prices?", "hire my first employee?", "raise or bootstrap?", "kill this project?" — and the council weighs in through their documented frameworks, surfaces where they disagree, and synthesizes a recommendation. Also use when the user mentions 'maker council,' 'board of advisors,' 'what would Bezos do,' 'what would Jason Fried say,' 'channel Naval,' 'ask the council,' 'get multiple perspectives on this decision,' or asks how a famous founder would approach their problem. Optional live-research pass grounds takes in what each member has actually said (via deep-research / watch-video / last30days). Sibling of marketing-skills' marketing-council (marketing questions go there; company-building and operator questions come here). Archives sessions to ~/.config/makerskills/maker-council/archive/. For committing to one of the surfaced directions, hand off to decide.
Manage this repo's agent skills with the skilly CLI — add or remove bundles/skills, pull hub updates. Use when the user wants skills or bundles added, removed, or updated. For a skills.sh URL use the skills CLI directly, not skilly. Not for repo bootstrap (that is `skilly setup`, run once).
Set up a new repository or apply Jess's repository tooling defaults when the user requests bootstrap, project infrastructure, or a full repository template. Do not use for ordinary coding, prototypes, or hardening that does not request repository setup.
**WORKFLOW SKILL** - First-run flow for adding Aspire to a repo. Picks `aspire new` (greenfield) or `aspire init` (existing repo), drops the AppHost skeleton, then hands off to `aspireify` for resource wiring. USE FOR: aspire init, aspire new, aspire-starter, aspire-ts-starter, aspire-py-starter, add Aspire to existing repo, scaffold Aspire app, bootstrap Aspire, no AppHost detected, install aspireify, apphost.mts, generated .aspire/modules. DO NOT USE FOR: AppHost wiring on an existing AppHost (use aspireify), start/stop/wait (use aspire-orchestration), deploy/publish (use aspire-deployment), logs/traces (use aspire-monitoring), repo that already has an AppHost. INVOKES: aspire CLI (init, new, doctor), aspireify (handoff after skeleton drop). FOR SINGLE OPERATIONS: Run `aspire init` or `aspire new TEMPLATE` directly.
One-time setup of import-linter contracts (in pyproject.toml) for a NEW python-ddd project, so the layered architecture (presentation → application → domain, a framework-free domain, infrastructure that only implements ports) is enforced by `lint-imports` — and therefore CI — from the first commit. Use when bootstrapping a new Python DDD backend's architecture enforcement, or adding it to a Python service that has none.
Use when bootstrapping a new Rust monorepo workspace from commit 1 — when the project has more than one binary crate (e.g. an API server and a background worker), when shared types must be consumed by two or more members without duplicating code, or when a single-crate layout would force one binary to carry another's compile-time dependencies. Triggers — a team wants shared wire contracts between a backend service and a worker process; a shared infrastructure primitive crate must stay independent of both consumers; the Cargo.toml at the repository root has no `[workspace]` section yet. Not applicable for single-crate projects (see rust-project-setup).
v2.5.0 — Use when bootstrapping, completing, updating, or auditing project documentation, or documenting a feature/module/epic: AGENTS.md + docs/, ADRs, roadmap, docs/features/<slug>/, docs/plans/<slug>/. Triggers: "document this project", "bootstrap docs", "sync docs", "audit docs", "docs vs code", "from zero", "new feature", "nueva feature", "promové el plan", "after ark-check", "arkgate bridge", "knowledge dashboard", /documentation-manager. Intents: integrate, audit, from-zero. Feature autopilot v2; Implementation bridge opt-in; ArkGate post-gate sync; dashboard HTML; polyglot + monorepo hubs; team governance (docs/team); living claims v0 + local CI structural audit (Knowledge OS first increment toward 100×). On conflict code wins.