Skip to main content
Manus에서 모든 스킬 실행
원클릭으로
GitHub 저장소

slidev-theme-dracula

slidev-theme-dracula에는 jd-solanki에서 수집한 skills 15개가 있으며, 저장소 수준 직업 범위와 사이트 내 skill 상세 페이지를 제공합니다.

수집된 skills
15
Stars
161
업데이트
2026-07-06
Forks
4
직업 범위
직업 카테고리 3개 · 100% 분류됨
저장소 탐색

이 저장소의 skills

automate-commit-based-gh-release-changelog
소프트웨어 개발자

Automate GitHub release creation and changelog generation from Conventional Commits using changelogithub — includes GitHub release mechanics, tag-based triggers, required permissions, and fetch-depth gotcha. Use when setting up GitHub releases, generating changelogs from commits, using changelogithub, or configuring v* tag triggers and contents:write permissions.

2026-07-06
automate-npm-release
소프트웨어 개발자

Automate npm package publishing via GitHub Actions for single-package repos and independent monorepo packages, including bumpp version tags, GitHub release notes, trusted publishing, provenance, and package-scoped release tags. Use when setting up or modifying npm publish workflows, npm release pipelines, version bumping, package-scoped monorepo releases, changelogithub release notes, trusted publishing, provenance badges, NPM_TOKEN, or OIDC publishing.

2026-07-06
clean-code
소프트웨어 개발자

Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "code review", "naming conventions", "function too long", "code smells", "readable code", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing pull requests for readability, refactoring messy functions, debating comment styles, or improving error handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture, see clean-architecture.

2026-07-06
code-organisation
소프트웨어 개발자

Decide where code lives — the directory tree, module and package boundaries, and the layout inside a file. Use when starting a new project or directory tree, placing a new file/class/function, grouping code into modules or packages, splitting an oversized file or module, naming directories/packages/files, separating source from generated build artifacts, or auditing an existing codebase's structure.

2026-07-06
coding
소프트웨어 개발자

Composition skill which invokes sub-skills for coding tasks. It is a meta-skill that orchestrates the use of other coding-related skills.

2026-07-06
comment-code
소프트웨어 개발자

Write clear, useful in-code comments and documentation that capture what the code cannot say for itself. Use this skill whenever writing or revising comments, docstrings, interface/API documentation, function or class headers, or inline explanations — and whenever reviewing code for comment quality or being asked to "document," "add comments," "explain in comments," or improve existing comments. Apply it even when the request only mentions writing the code, since fresh code is the moment to document it well.

2026-07-06
coding
소프트웨어 개발자

Composition skill which invokes sub-skills for coding tasks. It is a meta-skill that orchestrates the use of other coding-related skills.

2026-07-06
git-commit
소프트웨어 개발자

A skill to commit changes to a git repository, following conventional commit format.

2026-07-06
grill-me
프로젝트 관리 전문가

A relentless interview to sharpen a plan or design.

2026-07-06
grilling
프로젝트 관리 전문가

Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.

2026-07-06
implement
소프트웨어 개발자

Implement a piece of work based on a PRD or set of issues.

2026-07-06
node-cli
소프트웨어 개발자

Patterns and conventions for building Node.js CLI tools — src structure, entry point setup, Commander wiring, and update notifications. Use when creating or modifying a Node.js CLI, adding Commander commands, wiring update-notifier, or asking how to structure a CLI entry point or src directory.

2026-07-06
review
소프트웨어 품질 보증 분석가·테스터

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

2026-07-06
to-issues
프로젝트 관리 전문가

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

2026-07-06
to-prd
프로젝트 관리 전문가

Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

2026-07-06