Loading...
Loading...
Found 891 Skills
This skill helps users extract structured product listings from Amazon, including titles, ASINs, prices, ratings, and specifications. Use this skill when users want to search for products on Amazon, find the best selling brand products, track price changes for items, get a list of categories with high ratings, compare different brand products on Amazon, extract Amazon product data for market research, look for products in a specific language or marketplace, analyze competitor pricing for keywords, find featured products for search terms, get technical specifications like material or color for product lists.
Specifications and Methods for Character and Scene Extraction
Run tests against a validated RootSpec specification and report results. Use this when a user wants to run tests, check what's passing, get a test report, or verify their implementation works.
A brand product-launch email — masthead with wordmark, hero image block, headline lockup with skewed-italic accent, body copy, primary CTA, and a specifications grid. Pure HTML email layout (centered single column, table fallback). Use when the brief asks for an "email", "newsletter blast", "MJML", "product launch email", or "email template".
Use when the user asks to write specs before code, define acceptance criteria, plan features before implementation, generate tests from specifications, or follow spec-first development practices.
Build, update, and apply iOS design specifications using Apple Human Interface Guidelines (HIG) source data. Use when a task asks for iOS UI/UX rules, Apple design standards, component behavior, accessibility constraints, interaction patterns, or feature-level design-spec writing grounded in official HIG pages.
AI SDLC controlled change-workspace and specification-delta workflow. Use when an AI assistant needs to create or validate an isolated proposal workspace, author and validate requirement deltas, preview canonical changes, or apply and archive an explicitly approved change with rollback evidence. Supports `--quick-flow` for assumption-driven drafts and `--full-flow` for strict owner, target, evidence, and authority checks.
Produce a "production-ready, replica-grade" UI/UX R&D specification document package (directory isomorphic skeleton, common foundation, component/page contracts, coverage mapping, index and worklog) from the product PRD. Suitable for scenarios where PRDs need to be converted into front-end replicable specification documents, UI/UX R&D specifications, interface contracts and acceptance criteria; not recommended for requests that only require visual inspiration/pure UI appreciation or direct code implementation.
Writes and reviews structured Lean 4 proofs and designs Lean libraries following Mathlib conventions. Use when proving theorems in Lean, formalizing mathematics or specifications in Lean 4, defining new types or definitions in a Lean library, reviewing Lean proofs for readability and maintainability, refactoring long tactic proofs into lemmas, filling in sorry placeholders in a Lean development, setting up CI or linters for a Lean project, diagnosing slow proofs or maxHeartbeats timeouts, or writing custom tactics, macros, or linters.
Analyses a third-party system's API or file specification against Factorial's integrations framework and produces a detailed integration mapping document — the integration domain (payroll or finance), every capability in that domain with its verdict (fully, partially or not supported), the vendor endpoints to use for each, and the field-by-field mapping between Factorial's API and the vendor's. Use whenever someone shares a vendor API spec, OpenAPI/Swagger file, developer-portal link, integration guide or file layout and wants to know what we could build against it, how to map it, whether an integration is feasible, or asks for integration scoping, a fit-gap assessment or a field mapping. Use it even for informal asks ("can we integrate with this?", "how would new hires map to their API?") and partial specs.
Expert in requirements definition and system design. Converts abstract requirements into concrete specification documents (SPEC.md) and design documents (DESIGN.md), and visualizes system structures using Mermaid diagrams.
Embedded C Code Style Assistant, based on the code specifications of 51 MCU teaching projects. Uses snake_case as the default naming convention, with camelCase as an option. It is used to create project structures that comply with embedded development specifications, optimize code style, and provide hardware driver templates. Suitable for embedded C project development such as 51 MCU and STM32.