2,104 件 ・ 関連度順
概要と使いどころ
Structures board engagement for growth equity investments with meeting cadence, committee design, and information rights. Use when establishing board governance, preparing board materials, or managing investor board relationships.
日本語の概要は準備中です。原文の説明を表示しています。
Creates VC IC presentation materials with deal thesis, market analysis, team assessment, competitive landscape, and return scenarios. Use when preparing IC memos, presenting investment opportunities, or documenting investment decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates stapled secondary structures combining primary commitment with secondary purchase in coordinated transactions. Use when analyzing stapled deals, structuring combined primary/secondary, or evaluating staple economics.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates management fee designs with commitment-period vs invested-capital bases, step-downs, and offset provisions. Use when analyzing fee structures, comparing fee levels, or modeling fee revenue for GPs.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates cornerstone investment commitments with allocation guarantees, lock-up terms, and signaling value assessment. Use when structuring cornerstone tranches, analyzing anchor investors, or evaluating demand signals.
日本語の概要は準備中です。原文の説明を表示しています。
Git-aware smart revert for tracks, phases, and tasks. Handles rewritten history, finds related commits, and provides safe rollback with multiple confirmation gates.
日本語の概要は準備中です。原文の説明を表示しています。
Automated security scanning pipeline covering SAST (Semgrep), SCA (OWASP dependency-check), SBOM generation (Syft), vulnerability scanning (Grype), and secrets detection (detect-secrets). Invoked by security-architect for pre-commit gates, CI integration, and finding triage.
日本語の概要は準備中です。原文の説明を表示しています。
Verify fix commits address security findings without introducing new bugs or regressions. Analyzes diffs for anti-patterns like removed validation, weakened access control, reduced error handling, reordered external calls, and changed integer operations. Generates structured FIX_REVIEW_REPORT with finding status tracking.
日本語の概要は準備中です。原文の説明を表示しています。
Safe codebase cleanup: delete AI slop, consolidate duplicates, update imports — always test-verified before committing
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate HackerOne / Bugcrowd / Intigriti programs before committing time. Decide signal-to-noise, payout history, response time, scope size, and competition level. Use when the user is considering a new bug bounty target or asking "should I hunt this".
日本語の概要は準備中です。原文の説明を表示しています。
Draft a changelog for the next release by summarizing git commits since the last tag. Use only when the user asks to draft release notes, write a changelog entry, or prepare the next version's notes — never trigger automatically.
日本語の概要は準備中です。原文の説明を表示しています。
Act on the findings a review left on a PR or MR: take or decline each by severity, edit the code, one commit, reply. Use when handed a PR or MR URL that has already been reviewed. Edits real code.
日本語の概要は準備中です。原文の説明を表示しています。
Enforce Biome formatting and lint discipline in this repository. Use when making any file edits, when asked to run format/lint, and immediately before any commit. Always execute `bun run lint` (from package.json), apply resulting fixes, and re-run until clean. Treat `bun run lint:links` as optional by default, and recommend it when files under `content/` are changed.
日本語の概要は準備中です。原文の説明を表示しています。
Perform an adversarial review of the current uncommitted changeset, validating it against project contracts and architectural intent.
日本語の概要は準備中です。原文の説明を表示しています。
Run the SDLC validation pipeline using direct tool invocations. No wrapper scripts required. Use when checking code quality before commits or PRs.
日本語の概要は準備中です。原文の説明を表示しています。
Set up Android app signing safely — generate an upload keystore, enroll in Play App Signing, and wire a Gradle release signingConfig that reads secrets from a git-ignored keystore.properties / CI (never committed). Use when configuring signing for a Play release.
日本語の概要は準備中です。原文の説明を表示しています。
Reflective Memory. Use when working with memory, reflection, context management, or intent tracking. Provides the reflective memory practice — how and when to use keep tools for capturing insights, tracking commitments, and maintaining awareness.
日本語の概要は準備中です。原文の説明を表示しています。
Use when stress-testing a proposal, plan, architecture or decision before committing to it, such as pre-mortems, assumption audits, "should we even do this?" questions, or when everyone agrees too easily. Not for code review; it challenges strategy, approach and hidden risks.
日本語の概要は準備中です。原文の説明を表示しています。
Run a write-capable Kimi swarm that edits many disjoint targets in a throwaway worktree and returns a reviewable patch. Use only for explicit parallel edit fan-out requests; the plugin never applies or commits the patch.
日本語の概要は準備中です。原文の説明を表示しています。
Decide whether a protein has a pocket worth targeting, and where it is, before committing to a docking or design campaign. Use this skill to run fpocket cavity detection, rank cavities by druggability and volume, compare apo and holo conformations to spot induced fit, identify allosteric and cryptic cavities that only open in simulation, and convert a chosen cavity into the search box coordinates a docking run needs. Also trigger on fpocket, cavity detection, druggability score, alpha sphere, cryptic pocket, allosteric site, pocket volume, hotspot mapping, or undruggable target assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Assemble the human genetic evidence for and against a target before a programme commits to it — the evidence class that most improves the odds of surviving clinical development. Use this skill to pull gnomAD constraint metrics (LOEUF, pLI, observed/expected) that show whether loss of function is tolerated in people, retrieve GWAS Catalog associations and fine-mapped credible sets for a gene, and read a natural human knockout as a safety readout. Also trigger on gnomAD, LOEUF, pLI, loss-of-function intolerance, mutational constraint, GWAS Catalog, credible set, human knockout, genetic support, or target safety dossier.
日本語の概要は準備中です。原文の説明を表示しています。
Post-implementation self-review. Use AFTER finishing ANY code implementation or change — before declaring it done, committing, or opening a PR — to critique your own work: re-read the diff adversarially, confirm unit tests cover every branch/edge, kill duplication, follow clean-code/SOLID and the repo's own docs & invariants, decide if something should become documentation, update/prune memory, and strip outdated comments. Trigger it whenever you've just written or modified code and are about to wrap up, even if the user didn't explicitly ask for a review.
日本語の概要は準備中です。原文の説明を表示しています。
Review a pull request end-to-end using GitHub CLI. Covers diff analysis, commit history review, CI/CD check verification, severity-leveled feedback (blocking/suggestion/nit/praise), and gh pr review submission. Use when a pull request is assigned for review, performing a self-review before requesting others' input, conducting a second review after feedback is addressed, or auditing a merged PR for post-merge quality assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Run the jigsawR test suite via WSL R execution. Supports full suite, filtered by pattern, or single file. Interprets pass/fail/skip counts and identifies failing tests. Never uses --vanilla flag (renv needs .Rprofile for activation). Use after modifying any R source code, after adding a new puzzle type or feature, before committing changes to verify nothing is broken, or when debugging a specific test failure.
日本語の概要は準備中です。原文の説明を表示しています。