Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

cipradu

@cipradu source repo

34 published skills

  1. ▌
    Git Tag · cipradu bundle
    Use when listing, inspecting, verifying, creating, annotating, signing, publishing, comparing, deleting, recovering, or reconciling Git tags.
    0
    installs
  2. ▌
    API Design · cipradu bundle
    Use when designing, reviewing, or changing API contracts, endpoints, schemas, response shapes, error formats, pagination, versioning, OpenAPI/GraphQL contracts, idempotency, rate limits, or API security boundaries.
    0
    installs
  3. ▌
    Git Branch · cipradu bundle
    Use when inspecting, creating, switching, tracking, synchronizing, renaming, deleting, pruning, or assessing the safety of Git branches and linked worktrees.
    0
    installs
  4. ▌
    Git Commit · cipradu bundle
    Use when the user asks to commit changes, create a git commit, stage working-tree changes for commit, write or apply a commit message, split local changes into logical commits, or prepare committed history without pushing or opening a pull request.
    0
    installs
  5. ▌
    Microsoft365 · cipradu bundle
    Use when reading Outlook mail or Microsoft Teams content through Microsoft 365 MCP tools, including finding or searching email, reading a message body, browsing mail folders, and listing teams, channels, chats, or members, and when such a tool rejects a query parameter or returns 400, 403, or 429.
    0
    installs
  6. ▌
    Create Readme · cipradu bundle
    Use when creating, rewriting, validating, or substantially refreshing README.md or repository front-door documentation for a project, package, application, CLI, skill bundle, plugin, template, or monorepo.
    0
    installs
  7. ▌
    Create Skills · cipradu bundle
    Use when authoring, revising, debugging, testing, or deciding whether to create a reusable agent skill for recurring behavior, process, technique, tool, or reference work
    0
    installs
  8. ▌
    Project Rules · cipradu
    Use when starting or governing non-trivial AI-assisted project work, especially when approval, scope control, evidence, collaboration style, or complete output discipline matters.
    0
    installs
  9. ▌
    Github Actions · cipradu bundle
    Use when authoring, reviewing, securing, validating, optimizing, or orchestrating GitHub Actions workflow YAML, reusable workflows, trust paths, proof claims, release or container pipelines, environments, or OIDC.
    0
    installs
  10. ▌
    Github Release · cipradu bundle
    Use when preparing, inspecting, creating, updating, publishing, verifying, recovering, or coordinating GitHub Release records, notes, assets, release models, and delivery-state handoffs.
    0
    installs
  11. ▌
    Codebase Search · cipradu bundle
    Use when an answer requires repository content or relationships not already verified, including locating implementations, explaining cross-file behavior, tracing callers or usages, finding patterns, assessing change impact, reconciling code with project artifacts, investigating runtime clues, or gathering repository evidence for downstream work.
    0
    installs
  12. ▌
    Database Design · cipradu bundle
    Use when designing, reviewing, or changing relational database schemas, migrations, transactions, indexes, backfills, query behavior, ORM/database access patterns, soft deletes, tenancy, or database performance/concurrency.
    0
    installs
  13. ▌
    Visual Artifact · cipradu bundle
    Use when the user asks to understand a topic visually, see a code or system diagram, compare changes or quantities, or create a visual explanation or evidence-backed report from conversation, code, a PRD, spec, plan, or implementation result.
    0
    installs
  14. ▌
    Git Pull Request · cipradu bundle
    Use when the user asks to create, open, draft, update, inspect, monitor, or merge a hosted pull request or merge request; handle hosted review threads; prepare a title/body; decide draft or ready state; or push only as part of explicitly authorized PR work.
    0
    installs
  15. ▌
    Hindsight Memory · cipradu
    Use when Hindsight tools are available and the work requires storing or retrieving durable team operational memory — a user shares a lasting fact, correction, decision, or procedure; an incident is resolved; someone asks about prior incidents, device history, or whether a problem has happened before; or an explicit remember or recall request appears.
    0
    installs
  16. ▌
    Testing Strategy · cipradu bundle
    Use when designing, writing, reviewing, or planning software tests, verification evidence, or reusable project verification harnesses, including bootstrap, routine use, drift maintenance, and feature-map lifecycle decisions for runnable products.
    0
    installs
  17. ▌
    Create Project Adr · cipradu bundle
    Use when creating, revising, validating, or deciding whether to create a project Architecture/Technical Decision Record (ADR) for a significant accepted or proposed technical decision in a software project, including architecture, framework, UI/UX, data model, tooling, integration, or repeated implementation-pattern decisions.
    0
    installs
  18. ▌
    Create Project Prd · cipradu bundle
    Use only when the user explicitly asks to create, draft, revise, or validate a PRD for a project, product, or feature before engineering specification or implementation planning.
    0
    installs
  19. ▌
    Project Continuity · cipradu
    Use when starting, resuming, pausing, or closing meaningful project work where docs/progress.md or another project continuity artifact must preserve current state, blockers, next action, or alignment with active specs/plans.
    0
    installs
  20. ▌
    Python Engineering · cipradu bundle
    Use when writing, reviewing, refactoring, scaffolding, configuring, testing, packaging, securing, or optimizing Python code or Python project tooling — pyproject/uv/ruff/typing/pytest mechanics, settings, logging, async, performance, CI, Docker builds, or Python idioms.
    0
    installs
  21. ▌
    Architecture Design · cipradu bundle
    Use when designing or reviewing software architecture, module boundaries, service/tool separation, interface seams, adapter placement, cross-layer dependencies, or architecture-impacting refactors.
    0
    installs
  22. ▌
    Continuation Prompt · cipradu
    Use when the user asks for a continuation prompt, fresh-session briefing, or cross-agent, cross-person, or cross-harness context handoff that should prevent broad rediscovery of active work.
    0
    installs
  23. ▌
    Create Documentation · cipradu bundle
    Use when creating, revising, validating, or organizing reader-facing technical documentation such as tutorials, how-to guides, reference docs, explanations, API docs, architecture docs, runbooks, troubleshooting guides, docs sites, or docs updates that must stay aligned with source truth.
    0
    installs
  24. ▌
    Error Handling Design · cipradu bundle
    Use when designing, changing, or reviewing application error handling, runtime validation failures, error taxonomies, result envelopes, exception mapping, sanitized messages, retryability, fallback/degraded-mode behavior, error aggregation, cleanup, correlation IDs, logging, or redaction behavior.
    0
    installs
  25. ▌
    Git Resolve Conflicts · cipradu
    Use when resolving in-progress Git merge, rebase, cherry-pick, revert, stash, or pull conflicts; unmerged paths; conflict markers; ours/theirs choices; lockfile/generated-file conflicts; or branch integration conflicts before commit or PR work.
    0
    installs
  26. ▌
    Queue And Cache Design · cipradu
    Use when designing, reviewing, or changing queues, background jobs, worker processing, Redis-backed caches, cache invalidation, TTLs, Redis-backed locks, Redis-backed rate limits, Redis pub/sub or streams, retries, idempotency, dead-letter handling, or queue/cache observability.
    0
    installs
  27. ▌
    Typescript Engineering · cipradu bundle
    Use when writing, reviewing, refactoring, scaffolding, configuring, testing, packaging, securing, or optimizing TypeScript or JavaScript code, applications, packages, workspaces, or project tooling.
    0
    installs
  28. ▌
    Create Engineering Spec · cipradu bundle
    Use when a rough feature, bug report, compliance request, operational/domain/product note, or existing-system change must become an engineering-facing spec before planning, implementation, migration, or review
    0
    installs
  29. ▌
    Create Spec Readiness Map · cipradu bundle
    Use when an existing PRD, product brief, or requirements artifact is too broad or uncertain to become an engineering spec without first resolving multiple spec-readiness questions or one broad spec-readiness blocker across sessions.
    0
    installs
  30. ▌
    Create Implementation Plan · cipradu bundle
    Use when an approved engineering spec must become a deeply researched, dependency-ordered implementation plan before a human engineer or coding agent changes code
    0
    installs
  31. ▌
    Coding Project Orchestrator · cipradu bundle
    Use before acting on real-repository coding-project work when the correct workflow, current source authority, ceremony level, responsible downstream skill or agent, or acceptance gate must be chosen. Trigger on features, bugs, refactors, specs/plans, architecture, implementation, reviews, agents/skills/rules, source-control, external sync, or any request where missing truth, blast radius, verification, or responsibility is unclear.
    0
    installs
  32. ▌
    Create Implementation Pattern · cipradu bundle
    Use when creating, revising, validating, or deciding whether to create a reusable implementation pattern from repeated project code, review findings, ADR/spec/plan decisions, or post-implementation pattern-capture signals.
    0
    installs
  33. ▌
    Structured Problem Resolution · cipradu bundle
    Use before acting on any troubleshooting or failure signal or proposed diagnosis/fix, including broken or unexpected behavior, failed tests/builds/commands, runtime errors, performance/flaky/regression issues, review/bug-report/human/AI claims, repeated failed attempts, or drift-prone library/API/runtime behavior. Mandatory before diagnosis or fixes; turn signals into current evidence, hypotheses, impact analysis, and verified resolution.
    0
    installs
  34. ▌
    Implementation Review Workflow · cipradu bundle
    Use when implementation changes need independent review, reviewer dispatch, verdict interpretation, re-review, or completion-gate decisions
    0
    installs