knvpk
- 11 skills
- 0 followers
- 6 hours ago last updated
- ▌ Vibe Wiki · knvpk bundleBuild and maintain a persistent, compounding wiki from URLs and local files. Commands: wiki init, wiki ingest, wiki query, wiki lint, wiki help, wiki generate schema.
- ▌ Brainstorm · knvpk bundleRun a structured AI brainstorming session using one of 6 proven methods — Big Mind Mapping (broad idea generation), Reverse Brainstorming (invert the problem), Role Storming (multiple personas), SCAMPER (systematic transformation), Six Thinking Hats (balanced analysis), or Starbursting (question-first discovery). Use when the user wants to generate ideas, explore a problem, make a decision, or scope a project.
- ▌ Issue Explore · knvpk bundleFetches a work item from GitLab, GitHub, Jira, or Plane (auto-detected from the reference format or URL) and starts opsx:explore with the issue context and code repository context pre-loaded. Use when a user mentions a ticket number, issue key, or issue URL and wants to explore the implementation before starting a change. Works correctly when the issue tracker and the code host are different systems (e.g. Jira issues + GitLab code).
- ▌ Backend Scaffold · knvpkBootstrap files every new backend project needs — Nix dev shell, task runner, pre-commit/ruff for Python, and OpenAPI spec init. States this user's default tool for each concern and points to the dedicated convention skill for full rules. Use when starting a new backend service or repo from scratch, or when any of these foundational files are missing.
- ▌ Pre Commit Python · knvpkThe standard .pre-commit-config.yaml used across this user's Python projects — ruff (lint + format), pre-commit-hooks sanity checks, bandit security scanning, and pyupgrade for py312. Use when creating or editing .pre-commit-config.yaml in a Python project, or reviewing one for consistency with this user's other projects.
- ▌ Nix Best Practises · knvpkNix conventions and rules for projects using flake.nix — attribute set nesting style, required buildInputs, derivation file layout, flake description conventions, and the paired .envrc for direnv activation. Use when creating or editing a flake.nix or .envrc, adding packages/dependencies to a Nix flake, writing custom Nix derivations, or reviewing Nix code for style.
- ▌ Docker Modular Stack · knvpk bundleDefine, scaffold, and lint Docker services for any project. Three modes: (1) Scaffold — copy curated templates (postgres, valkey, grafana, langfuse, litellm, 30+ more) into a new project with generated docker-compose.yaml, .env, and Taskfile; (2) Add — given any tool's documentation, derive a compliant service.yaml from scratch; (3) Lint — validate any service definition against the project's conventions. Use when setting up a docker stack, adding a new docker service from docs, or checking whether a service definition is correct.
- ▌ Justfile Conventions · knvpkConventions for justfile (Just command runner) files observed across this user's older projects — dotenv loading, [doc('...')] recipe descriptions, shebang recipes for multi-line scripts, and variable declarations. Use when creating or editing a justfile/Justfile, adding recipes to a project, or reviewing a justfile for style. Note this user's newer projects use Taskfile.yaml instead — see [[taskfile-conventions]] — prefer that for new projects unless the user asks for Just specifically.
- ▌ Taskfile Conventions · knvpkConventions for Taskfile.yaml (go-task) files observed across this user's projects — version pinning, dotenv loading, environment-aware vars, colon-namespaced task names, and desc usage. Use when creating or editing a Taskfile.yaml/Taskfile.yml, adding tasks to a project, or reviewing a Taskfile for style.
- ▌ Secretspec Conventions · knvpkConventions for secretspec.toml (declarative secrets manifest) used across this user's projects — schema shape, provider configuration, the newer-than-nixpkgs Nix override, and the Taskfile export task. Use when creating or editing secretspec.toml, wiring secretspec into a flake.nix or Taskfile.yaml, or reviewing secrets handling for a project.
- ▌ Terraform Design Guide · knvpkTerraform AWS infrastructure design patterns, naming conventions, module structure, IAM, Lambda, RDS, S3, and security baselines. Use when starting a new infra repo, adding a Terraform module, naming resources, writing IAM policies, setting up Lambda stubs, configuring S3 buckets, or applying security controls.