tsdown-package
openbooklet.com/s/tsdown-packageopenbooklet.com/s/tsdown-package@1.0.0GET /api/v1/skills/tsdown-packageMigrates a monorepo package from `tsup` to `tsdown`. Use when asked to migrate a package to `tsdown` and the package has used `tsup` thus far.
Bumps `biome` package versions (e.g. `@biomejs/biome`) using `pnpm`, aligns `biome.jsonc` files with the new version/s across the repository and runs biome-related checks. Use when required to update `biome` to a newer version - explicitly or implicitly (e.g. after running `pnpm up`, `pnpm update`, `pnpm upgrade` without specific package names).
Create a new transient project workspace under projects/<project>/ (folders + optional stub docs), then hand off to drive-create-spec / drive-generate-plan.
Generate and iteratively refine engineering specs from a description, conversation summary, or blank template. Use when the user wants to create a spec, PRD, product requirements document, write up requirements, or spec out a feature. Also use when summarising a conversation into a spec.
Generate an execution plan from a spec, with milestones, tasks, and test coverage for all acceptance criteria. Use when the user wants to plan a project, break a spec into milestones, generate tasks from a spec, or create an execution plan. Optionally creates a Linear project.
Generate local PR/branch review artifacts for the current branch vs its base - an in-repo canonical spec (if present) or an inferred review `spec.md`, plus `system-design-review.md`, `code-review.md`, and `walkthrough.md` (via `.agents/skills/drive-pr-walkthrough/SKILL.md`). Writes artifacts to disk (next to the in-repo spec when present, otherwise under `wip/`). Use when the user asks for a local PR/branch review, a code review, a system design review, to "review this branch", or to produce written review docs. Do not modify implementation code.
Auto-indexed from prisma/prisma-next
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.