Loading...
Loading...
Found 1,872 Skills
Build or transform ecommerce websites from loose company, product, or brand briefs into unconventional, brand-specific shopping experiences with original ImageGen product imagery. Use when a user asks for a crazy, wild, experimental, unconventional, anti-template, art-directed, or highly memorable online store; wants Codex to invent an ecommerce visual direction from business details; or wants a working storefront that combines creative concepting, generated product photography, responsive implementation, cart interactions, validation, and optional publishing.
Use when writing or editing code in an existing codebase — before adding comments, docstrings, try/catch blocks, validation, logging, or TODOs the surrounding file doesn't have, and before explaining your style choices in the reply.
Core skill for Sa-Token, a lightweight Java authentication and authorization framework. It covers login authentication, permission/role authentication, annotation-based authorization, route-interceptor authorization, Session management, forced logout, Token expiration strategies, framework configuration, Token styles and submission prefixes, frontend-backend separation, remember-me mode, mutually exclusive login on the same device, and handling NotLoginException scene values. StpUtil is the core facade utility class and provides a complete suite of authentication APIs, including login/checkLogin/logout/isLogin/getLoginId/getTokenValue. Use this skill when users need to integrate permission authentication into Java Web projects, use StpUtil for login and permission validation, configure route interceptors, or implement annotation-based authorization. It does not cover advanced features such as secondary authentication, account banning, multi-account support, SSO, OAuth2, microservices, API security, JWT, or Redis; use the corresponding specialized skills for those.
Diagnose and repair reproducible, intermittent, environment-specific, or production-observed software failures by tracing evidence to a root cause. Use when a symptom exists but its cause is uncertain or when a proposed fix needs causal validation. Do not use for feature implementation, speculative cleanup, or a general review without a concrete failure.
Use when bringing 3D assets into Roblox Studio or preparing avatar items: import from Blender, GLB, FBX or OBJ files, AI-generated or image-to-3D meshes (Scenario or other tools), wrong scale or size in studs, mesh faces the wrong way, too many triangles, mesh fails validation, holes or non-watertight meshes, textures too big or blurry, SurfaceAppearance and PBR maps, metalness or normal maps look wrong, rigid accessories and hats, UGC items, Accessory Fitting Tool, out of bounds, AvatarCreationService validation, EditableMesh or EditableImage previews, or generate_mesh.
Creates a new venue-profile YAML for venues/conferences/ from a conference CFP URL, validates it against venues/schema.yml, and preps the contribution PR. Use when the user wants to add a venue, contribute or refresh a venue profile, encode a conference's submission requirements (deadlines, page limits, blind level, template invocation, rebuttal format, submission system) as machine-readable YAML, copy a profile forward to a new year, or validate a profile before opening a pull request. Covers scaffolding the file, extracting facts from the live CFP, the DBLP/Semantic Scholar/Crossref alias table, the mandatory verified provenance block, schema validation, and PR-readiness checks.
Hunt MFA / 2FA bypass — 7 distinct patterns. (1) MFA not enforced on sensitive endpoints (password change, email change accept without MFA challenge), (2) MFA-step skip via direct navigation to post-login URL, (3) MFA-token replay (same code accepted twice), (4) brute-force the 6-digit OTP without rate limit (10^6 attempts at server speed), (5) race condition on OTP validation, (6) recovery-code dump via /api/me, (7) backup factor downgrade (SMS factor with no rate limit). Plus the chain: cookie theft + password oracle + no step-up = ATO without MFA challenge. Detection: trace auth flow in Burp, find every state transition, check if MFA is middleware-gated vs per-endpoint, check OTP entropy and rate limit on OTP-validate. Validate: attacker session reaching post-MFA state. Use when hunting auth bypass, MFA flows, chaining primitives toward ATO.
Analyzes code, CI/CD workflows, and container config for security vulnerabilities and compliance risks, producing fitness scores (1-10) across input validation, authentication/authorization, data protection, dependency security, error handling/logging, and cryptography. Use when the user says "security review", "check vulnerabilities", "audit security", "security issues", /review:review-security, asks to audit GitHub Actions workflows or a Dockerfile for security, or wants security fitness scores before shipping. Only reports findings with confidence >= 7/10.
Use when the user wants to extend an existing Spree 6 model or API controller without forking — add an association to Spree::Product, add a validation or scope, add a method to Spree::Cart / Spree::Order, narrow what an API v3 endpoint returns, permit an extra attribute on writes. Common phrasings include "add brand to product", "decorate Spree::X", "ProductDecorator", "OrderDecorator", "Module#prepend", "spree:model_decorator", "spree:controller_decorator", "extend an existing Spree model", "add a method to Spree::Order", "override Spree behavior", "monkey patch Spree", "customize an API controller". Provides the decorator pattern, the generators, the prepended(base) idiom, API controller decorators and the gotchas — and routes behavioral changes to workflow hooks, events or dependencies instead.
Migrate a user's project from Wot UI v1 to v2. Invoke this skill when the user requests upgrading wot-design-uni to @wot-ui/ui, replacing legacy components/APIs, migrating the form validation system, migrating icon names, or fixing compilation errors, blank icons, and runtime errors caused by v2 breaking changes.
Audits an Infrahub repository against best practices and rules, producing a structured compliance report. TRIGGER when: reviewing repo for compliance, onboarding to existing project, pre-deployment validation, catching issues. DO NOT TRIGGER when: creating schemas, writing checks/generators, querying live data, populating objects, planning an Infrahub version upgrade (use infrahub-planning-upgrades).
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes