Total 40,410 skills
Showing 12 of 40410 skills
Provision instant temporary Postgres databases via Claimable Postgres by Neon (pg.new) with no login, signup, or credit card. Use when users ask for a quick Postgres environment, a throwaway DATABASE_URL for prototyping/tests, or "just give me a DB now". Triggers include: "quick postgres", "temporary postgres", "no signup database", "no credit card database", "instant DATABASE_URL".
Machine learning development with JAX, functional programming patterns, and high-performance computing.
Code Porter Skill: Prioritize adopting excellent open-source projects, avoid reinventing the wheel unnecessarily. Use when: You need to implement new features, select technical solutions, or evaluate whether to build something from scratch. Triggers: "implement", "develop", "create", "build", "write a", "make a"
Web crawling and scraping with analysis. Use for crawling websites, security scanning, and extracting information from web pages.
Use when working on the spec branch of sdlc-dev, when requirements are ambiguous, scope is unstable, constraints are unclear, and issues such as context drift, unfounded assumptions, multiple questions asked at once, or requests to skip the FEATURE_DIR/raw gate occur.
Used to confirm that development is completed and ensure all tests/checks have passed
Responsible AI development and ethical considerations. Use when evaluating AI bias, implementing fairness measures, conducting ethical assessments, or ensuring AI systems align with human values.
Use when you need to produce a D2 decision document (RFC/Decision Doc) for a Spec Pack, and need to independently decide whether to execute D0 (bypass design via diversion) and D1 (optional research) even under pressure, avoiding guessing FEATURE_DIR, making up input details, writing design as implementation specifics, or leaving behind TODO/To-Confirm lists.
Use when you need to perform D1 research during the Spec-level design phase (output `{FEATURE_DIR}/design/research.md`), or when you face critical uncertainties/high-risk points that require verification first instead of directly proceeding to D2; common symptoms include lack of evidence to support trade-offs, unknown items written as TODOs/to-be-confirmed issues, attempting to guess the FEATURE_DIR under pressure, or writing research as implementation details.
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
自愈：扫描 topics.md 一致性并修复