Results for “pre-tool-use”

Stops AI from generating boring, generic UI. Use when building new interfaces, reviewing generated UI, or fixing the flat / generic look that AI tools default to. Anti-slop design principles for premium frontends.

Forces AI agents to investigate before editing or running destructive commands, improving code quality by requiring concrete facts like importers, data schemas, and user instructions.

Use when serving as a peer reviewer and deciding whether and how AI may assist, when a manuscript under review must never be pasted into an external tool, or when a confidentiality-preserving review and disclosure are needed.

Self-contained code review checklist — formatting, type safety, duplication, readable conditions, logic-out-of-UI, test coverage, comment quality. Adapts to whatever tooling the project actually has (skips Prettier/TypeScript/test-runner checks if unconfigured). Use before merging, after completing a feature, or any time you want a second pass on code quality. In Claude Code, prefer the official `code-review` skill or `pr-review-toolkit`/`feature-dev` code-reviewer agents instead — both are real, installed, and go deeper than this checklist. This copy exists for Codex/Cursor portability, where those agents aren't available.

Simulates open quantum systems with QuTiP, the Quantum Toolbox in Python, solving Lindblad master equations (mesolve), Monte Carlo trajectories (mcsolve), and unitary dynamics (sesolve). Use when studying master-equation or Lindblad dynamics, decoherence, dissipation, quantum optics, cavity QED, or open-system time evolution. NOT for circuit-based quantum computing or hardware execution — for IBM Quantum circuits prefer alterlab-qiskit, for Google Quantum AI or NISQ circuits prefer alterlab-cirq, and for gradient-trained quantum ML prefer alterlab-pennylane. Part of the AlterLab Academic Skills suite.

Research existing tools, libraries, and patterns before writing custom code by invoking a researcher agent.

Use when a commit's changes are finished and about to be presented for review. Runs the checks that catch the objections the user would otherwise raise, before they spend time reviewing.

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

Internal technical readiness drill assistant for release and handoff.

Guides a research-before-coding workflow, searching existing tools, libraries, and patterns before writing custom code, with decision matrices and integration with agent workflows.

Guides the agent to research existing tools, libraries, and patterns before writing custom code, using parallel searches across package registries, MCP servers, skills, and GitHub, then evaluating and deciding to adopt, extend, or build.

Evaluates a local pre-trade checklist before manual order entry, blocking planless, oversized, revenge-risk, market-regime-blocked, or circuit-breaker-blocked entries while journaling the decision for later review.

研究优先于编码的工作流程。在编写自定义代码之前，搜索现有的工具、库和模式。调用研究员代理。

Interactive walkthrough for new users. Learn by doing — each step creates real content in your vault. Three tracks (researcher, manager, personal) with a universal learning arc. Triggers on "/tutorial", "walk me through", "how do I use this".

Use before starting any new work to check for existing knowledge. This skill provides a systematic search and retrieval process for finding relevant knowledge from memory systems (PARA, Gigabrain, OpenStinger, existing skills) before starting work, preventing redundant effort and leveraging prior learning.

Flyway database migrations for Spring Boot applications. Covers migration scripts, versioning, callbacks, and rollback strategies. Based on production patterns from castellino and gestionale-presenze projects. USE WHEN: user mentions "flyway", "database versioning", "Java migrations", "Spring Boot migrations", "V1__", "migration checksum" DO NOT USE FOR: general migration strategies - use `migrations` instead, Liquibase - use specific tool skill, Prisma/TypeORM - use respective skills

Use when using Probe SDK.

Load this skill when the user says "prepare base", "prepare-base", or "/prepare-base". Prunes remote tracking references, checks out a base branch, pulls latest, and cleans up local-only feature branches after confirmation.

Use before any creative or ambiguous work - new features, new components, or behavior changes - to explore intent, requirements, and design before implementation starts.

在启动一个重要项目或关键行动之前，用于主动识别和防范风险

在启动高风险项目或重要决策前，需要预先识别潜在失败点以增强心理韧性和方案鲁棒性时

Use before sensitive, clinical, identifying, or raw interview data is placed in front of an AI tool, when transcripts or student materials need de-identification, or when a data-minimization gate must run before any analysis or drafting.

Runs before every git commit on heleni-memory. Checks: no credentials in tracked files, no oversized files, valid SKILL.md frontmatter for any new/modified skill. Triggers: "commit", "before push", "validate repo", or auto-runs as a git pre-commit hook.

Run a pre-mortem — imagine the project has already failed one year from now and work backward to find the root causes before they happen. Load when the user asks for a pre-mortem, wants to imagine failure before committing, asks "what could go wrong before we start", "assume this fails — why", "risk analysis before launch", "what kills this project", "what could go wrong", or when deep-thinking diagnoses a pre-mortem frame. Based on Gary Klein's prospective hindsight method, which surfaces failure causes more effectively than forward risk analysis. Most useful right before a major commitment.

Use /onboard for a focused Cursor onboarding flow that learns basic preferences, picks a first goal, and routes the user to the right next action.

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

Scaffolds a program.md research program for autoresearch by auto-detecting codebase signals and interviewing for missing details.

Pre-push hygiene check for GitHub repositories. Scans for PII, secrets, and sensitive data before pushing. Audits commit messages, enforces repo-specific blocklists, and rate-limits pushes to avoid GitHub abuse detection. Use before any git push, especially to public repos.

Use only for developer-facing products; analyze install, quickstart, first success, debugging, and production adoption journeys

Product Advisor