All authors
Claude Skills by Bluestep-Systems
github.com/Bluestep-Systems35 skills0 installs35 views
- Bspecs TriageTriage the AI.List feedback inbox — dedup, verify claims against shipped source, tag, assign, and move every triaged task out of "Open" so status is the state machine. Use when new ai-plugin feedback has accumulated on ClickUp, or on request ("triage the board", "any new issues?").Votes: 0GitHub stars: 3
- Quick TaskShort workflow for small tasks and bug fixes that don't warrant a full 3-phase spec. Use for clearly-scoped changes and bugs in this repo.Votes: 0GitHub stars: 3
- Release EmailDraft and queue a BlueStep-branded release-update email across three products (the bluestep-tools plugin, the b6p CLI, and the gateway MCP) since the last-sent watermarks. Maintainer-only, repo-local, manual — reads watermarks from a browser tab signed in to the outbox org, collects changes (CHANGELOG / gh / ClickUp), renders the email-safe template, queues an entry on the BlueHQ outbox form behind an in-session approval gate, drives the test send, and hands the human the signature step that ...Votes: 0GitHub stars: 3
- Spec CreateStart a new spec-driven feature. Creates requirements.md, then design.md, then tasks.md with explicit user approval between each phase. Use when the user wants to plan a non-trivial change to this repo (BlueStep's agent plugins repo).Votes: 0GitHub stars: 3
- Spec ExecuteExecute one task from a feature spec. By default delegates implementation to the spec-task-implementer subagent (isolated context); pass --inline to implement in the main session. Updates the task checkbox when done. Use after `/spec-create` has produced an approved tasks.md.Votes: 0GitHub stars: 3
- Spec StatusShow progress of all feature specs in `.claude/specs/`. Use when the user wants a summary of what's in flight.Votes: 0GitHub stars: 3
- B6p AuditCompare a local component's state against what lives on the BlueStep platform, listing files that differ. Use when the user wants to know if they (or someone else) changed something on the platform side, or before a push, to see what changed there before the push stops to ask about it.Votes: 0GitHub stars: 3
- B6p PullPull a B6P component from the BlueStep platform into the local workspace using its DAV URL, and scaffold draft/README.md if missing. Use when the user wants to bring a component down for the first time or re-sync after platform edits.Votes: 0GitHub stars: 3
- B6p PushPublish a BlueStep (B6P) component's local changes to the platform with the b6p CLI — make it live, deploy it, upload it, ship a fix — or save them as a draft only. Use whenever the user wants local edits of a component on the platform, even without the word "push" ("publish this", "make it live", "deploy my changes", "upload the fix", "put it on the platform"). It shows what changed, asks whether to publish or save a draft, and stops to ask before anything on the platform is overwritten or d...Votes: 0GitHub stars: 3
- B6p SetupSet up, check or bring up to date the BlueStep (B6P) tooling for this machine and this folder in one run — the b6p CLI and its login, the bluestep-tools plugin for your agent tool, the platform token and a live check of the gateway MCP, and the project files (a short AGENTS.md with the always-on rules, the CLAUDE.md bridge, README, settings) — writing what is missing, migrating what an older release wrote, keeping every project rule. Use it on a new machine, in a new or existing project, afte...Votes: 0GitHub stars: 3
- Bluestep ReferenceOn-demand BlueStep (B6P) platform reference — BsJs/RelateScript patterns, conventions, and gotchas. Consult when implementing, reviewing, or documenting a BlueStep component. This file is the manifest of single-topic instruction files (reference/, conventions/, gotchas/) with a one-line "load when" trigger for each; read it first to pick the right file.Votes: 0GitHub stars: 3
- Bluestep Vite ReportScaffold an off-platform Vite/Preact SPA merge-report project — check Node 20, run create-vite (preact-ts), set base "./", wire the deploy-lib config block + repository field, then print the [PLATFORM] report-creation and GitHub-repo steps for the human to execute. Use when starting a new Vite/Preact single-page-app merge report (the report serves a bundled static/index.html deployed via deploy-lib, not the CLI-compiled static/script.ts path).Votes: 0GitHub stars: 3
- Bspecs FeedbackSend a bspecs tooling-change request (a rule, skill, subagent, hook, reference file, spec/module template, or a shipped AGENTS.md rule) upstream to the team's tracker. Use when you or the user notice something about the bluestep-tools or bluestep-one plugin itself that should change — the plugin is a read-only shared install, so a lasting fix has to land upstream in the repo.Votes: 0GitHub stars: 3
- Quick TaskShort workflow for small tasks and bug fixes that don't warrant a full 3-phase spec. Keeps one living markdown doc for review during implementation. Use for clearly-scoped changes and bugs in a BlueStep component.Votes: 0GitHub stars: 3
- Spec CreateStart a new spec-driven feature. Creates requirements.md, then design.md, then tasks.md with explicit user approval between each phase. Use when the user wants to plan a new feature inside an existing component.Votes: 0GitHub stars: 3
- Spec ExecuteExecute one task from a feature spec. By default delegates implementation to the b6p-task-implementer subagent (isolated context); pass --inline to implement in the main session. Updates the task checkbox when done. Use after `/spec-create` has produced an approved tasks.md.Votes: 0GitHub stars: 3
- Spec StatusShow progress of all feature specs in `.claude/specs/`. Use when the user wants a summary of what's in flight.Votes: 0GitHub stars: 3
- Task CommentDraft a standardized implementation comment for a ClickUp task after a fix or feature is shipped. Handles both org-propagated (component-based) and direct (code-only) changes.Votes: 0GitHub stars: 3
- Bspecs FeedbackSend a bspecs tooling-change request (a rule, skill, subagent, hook, reference file, spec/module template, or a shipped AGENTS.md rule) upstream to the team's tracker. Use when you or the user notice something about the bluestep-tools or bluestep-one plugin itself that should change — the plugin is a read-only shared install, so a lasting fix has to land upstream in the repo.Votes: 0GitHub stars: 3
- BuildBuild, publish and check a BlueStep One custom component, one gate at a time — fresh types, type check and tests, copies check, required-fields check, push to draft, build over /gql from a signed-in tab, publish only a new sha that built green, served-sha check after a full reload, a measured UX check of the served screen against the project's thresholds, live check on your own test record, and for a UI change the design check against an approved canvas export. Also clones and sets up a new c...Votes: 0GitHub stars: 3
- ReferenceOn-demand reference for building BlueStep One custom components — the type files and a component repo's setup, the type, copies and required-fields checks, build and publish from a signed-in tab, the served and UX checks, the design check, and the rules, patterns and gotchas of the host, the kit, /gql reads and writes, rights, pages and tooling. This file is the manifest, one line per file with a \"Load when\" trigger; read it first, then only the file you need. Use when building, reviewing o...Votes: 0GitHub stars: 3
- SetupSet up or check a BlueStep One component workspace on Claude Code — checks the machine (bluestep-tools and its platform token, Node 20+, git access to the BlueStep One git host, the Claude desktop app's built-in browser pane and a sign-in on the BlueStep One host), then writes what the folder lacks: .claude/bluestep-one.json (the BlueStep One host and git host, the components, the test-data prefix), AGENTS.md, the CLAUDE.md bridge and .claude/settings.json. Asks only for BlueStep One values. ...Votes: 0GitHub stars: 3
- B6p AuditCompare a local component's state against what lives on the BlueStep platform, listing files that differ. Use when the user wants to know if they (or someone else) changed something on the platform side, or before a push, to see what changed there before the push stops to ask about it.Votes: 0GitHub stars: 3
- B6p PullPull a B6P component from the BlueStep platform into the local workspace using its DAV URL, and scaffold draft/README.md if missing. Use when the user wants to bring a component down for the first time or re-sync after platform edits.Votes: 0GitHub stars: 3
- B6p PushPublish a BlueStep (B6P) component's local changes to the platform with the b6p CLI — make it live, deploy it, upload it, ship a fix — or save them as a draft only. Use whenever the user wants local edits of a component on the platform, even without the word "push" ("publish this", "make it live", "deploy my changes", "upload the fix", "put it on the platform"). It shows what changed, asks whether to publish or save a draft, and stops to ask before anything on the platform is overwritten or d...Votes: 0GitHub stars: 3
- B6p SetupSet up, check or bring up to date the BlueStep (B6P) tooling for this machine and this folder in one run — the b6p CLI and its login, the bluestep-tools plugin for your agent tool, the platform token and a live check of the gateway MCP, and the project files (a short AGENTS.md with the always-on rules, the CLAUDE.md bridge, README, settings) — writing what is missing, migrating what an older release wrote, keeping every project rule. Use it on a new machine, in a new or existing project, afte...Votes: 0GitHub stars: 3
- Bluestep ReferenceOn-demand BlueStep (B6P) platform reference — BsJs/RelateScript patterns, conventions, and gotchas. Consult when implementing, reviewing, or documenting a BlueStep component. This file is the manifest of single-topic instruction files (reference/, conventions/, gotchas/) with a one-line "load when" trigger for each; read it first to pick the right file.Votes: 0GitHub stars: 3
- Bluestep Vite ReportScaffold an off-platform Vite/Preact SPA merge-report project — check Node 20, run create-vite (preact-ts), set base "./", wire the deploy-lib config block + repository field, then print the [PLATFORM] report-creation and GitHub-repo steps for the human to execute. Use when starting a new Vite/Preact single-page-app merge report (the report serves a bundled static/index.html deployed via deploy-lib, not the CLI-compiled static/script.ts path).Votes: 0GitHub stars: 3
- Bspecs FeedbackSend a bspecs tooling-change request (a rule, skill, subagent, hook, reference file, spec/module template, or a shipped AGENTS.md rule) upstream to the team's tracker. Use when you or the user notice something about the bluestep-tools or bluestep-one plugin itself that should change — the plugin is a read-only shared install, so a lasting fix has to land upstream in the repo.Votes: 0GitHub stars: 3
- Quick TaskShort workflow for small tasks and bug fixes that don't warrant a full 3-phase spec. Keeps one living markdown doc for review during implementation. Use for clearly-scoped changes and bugs in a BlueStep component.Votes: 0GitHub stars: 3
- Spec CreateStart a new spec-driven feature. Creates requirements.md, then design.md, then tasks.md with explicit user approval between each phase. Use when the user wants to plan a new feature inside an existing component.Votes: 0GitHub stars: 3
- Spec ExecuteExecute one task from a feature spec. By default delegates implementation to the b6p-task-implementer subagent (isolated context); pass --inline to implement in the main session. Updates the task checkbox when done. Use after `/spec-create` has produced an approved tasks.md.Votes: 0GitHub stars: 3
- PlanStart a spec for work that needs design. Writes requirements.md, then design.md, then tasks.md under .claude/specs/<feature>/, with explicit approval between each. Use when the user wants to plan a feature or a change that touches several parts of a repo; for a small scoped change, use /task.Votes: 0GitHub stars: 3
- Repo SetupAudit or create a repo's agent setup — the AGENTS.md rules file, the CLAUDE.md bridge, and a skill per repo workflow. Use this whenever the question is whether a repo's rules still match what it actually builds, tests and deploys: a command CI runs that the rules never mention, a command in the rules that no longer exists, rules that live only in CLAUDE.md so Cursor and Codex see nothing, or a repo with no AGENTS.md at all. Reach for it after a repo gains a test framework, a CI check, a deplo...Votes: 0GitHub stars: 3
- TaskShort workflow for a small, clearly scoped change or bug fix. Keeps one living document at .claude/tasks/<slug>.md with goal, files, done-when check, decisions and state, so the next session (or another tool) can pick it up without the transcript. Also runs the tasks of an approved spec, one at a time or all remaining ones in a row (in parallel where file lists are disjoint). Use for work that does not need design; for a feature, use /plan.Votes: 0GitHub stars: 3