All authors
Claude Skills by kalinichenko88
github.com/kalinichenko8814 skills0 installs0 views
- InfographicUse when drawing or updating the scenario pictures in docs/ that a skill's README links, or when a change makes one of them false.Votes: 0GitHub stars: 2
- ReleaseUse when releasing the craft plugin from main.Votes: 0GitHub stars: 2
- Plans> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking. **Goal:** Add `kalinichenko:roadmap`, a GitHub-backed PM skill that plans milestones and answers "what to take now / in parallel / what closes M1", and close the assignment gaps in `kalinichenko:github` take-in. **Architecture:** Bash scripts read GitHub with `gh`; each pag...Votes: 0GitHub stars: 2
- Plans> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking. **Goal:** Ship `kalinichenko:architecture`: its `SKILL.md`, and `invariants.sh`, which runs the `Check:` lines of a project's `docs/ARCHITECTURE.md`, with its test in `make check`. **Architecture:** One bash script, `skills/architecture/scripts/invariants.sh`. An awk parser...Votes: 0GitHub stars: 2
- Plans> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking. **Goal:** Add `kalinichenko:product`, a skeptical analyst that asks whether a task is worth doing before the work, and wire it into the architecture and review-loop skills. **Architecture:** The skill is text: `skills/product/SKILL.md` with two files beside it, one for the ...Votes: 0GitHub stars: 2
- ArchitectureUse when starting a new feature (a screen or page, an endpoint, a module or an integration), or at an architecture decision — where new code goes; a new module, layer, dependency, pattern or data store; a choice between options in a spec or a plan; or a change to a file or module past its size limit. Also when writing or checking docs/ARCHITECTURE.md, its invariants, or an ADR.Votes: 0GitHub stars: 2
- DebtUse when mapping a repository's technical debt — finding hotspots, files that break the layer rules of the project's instruction file or the invariants of its docs/ARCHITECTURE.md, duplicated code, over-engineering, or rules that the instruction files and docs/ARCHITECTURE.md repeat or contradict — and filing or re-measuring debt issues for refactoring.Votes: 0GitHub stars: 2
- DockerUse when writing or reviewing a Dockerfile, a compose file, a .dockerignore or a container entrypoint script — adding or bumping any image reference (FROM, COPY --from, an image under a service), choosing a base image, wiring Dependabot or Renovate for images, or a container that takes ten seconds to stop.Votes: 0GitHub stars: 2
- GithubUse when touching a repository's GitHub surface — writing a commit message, running `gh pr create` or merging a pull request, filing or updating an issue, picking an issue up to work on (including a bare `#91` or issue URL as the whole message), checking whether a finding is already filed, or creating or editing a GitHub Actions workflow.Votes: 0GitHub stars: 2
- ProductUse when a feature starts (a new capability, or a change of what the product does for its users), when a bug fix changes business logic, when a branch or pull request is reviewed (someone else's that changes code or behaviour, or one's own that adds a capability or changes what the product does, with no report of its worth), when brainstorming asks a question that chooses between ways, when a decision concerns the whole project (the licence, open source or not, distribution, pricing, the mone...Votes: 0GitHub stars: 2
- React ConventionsUse when writing or reviewing React code — adding a feature beside existing ones, placing a sub-component's hook, helper or constant inside a feature, importing from another feature or layer, letting one feature use another, registering a reducer, route or provider, holding a request's loading, error and data in a component, putting two requests in one component (loading its options and creating an option), reading a value from useRef or writing usePrevious, setting up the app's layout or rou...Votes: 0GitHub stars: 2
- Review LoopUse when a change is reviewed, before or after its pull request opens — running /code-review or /security-review in Claude Code or /review in Codex, sending a review subagent, choosing a review level, deciding whether another round is needed, or handling the findings a review or a person's review comments return. Also at the builder check of superpowers:brainstorming and after the self-review of superpowers:writing-plans.Votes: 0GitHub stars: 2
- RoadmapUse when planning a product's roadmap or milestones, asking which task to take next or what can run in parallel, asking what is left to close a milestone, putting a task off to Later, re-planning after a milestone closes, triaging new issues that have no label or no milestone, or when an agent needs the project's roadmap as context.Votes: 0GitHub stars: 2
- Typescript ConventionsUse when writing or reviewing TypeScript — declaring an object shape, placing a type, an enum or a schema that several files use, naming a new file or a constant, writing a callback, reaching for a dependency — or when setting up lint rules for a new TypeScript project.Votes: 0GitHub stars: 2