FRS Creation
Create detailed Functional Requirements Specifications for technical teams implementing Web, Mobile, ERP, CRM, CDP, and E-commerce solutions
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 11-21 00:15
258,901 results
Create detailed Functional Requirements Specifications for technical teams implementing Web, Mobile, ERP, CRM, CDP, and E-commerce solutions
Use when authoring or modifying a Datex Studio action (configurationTypeId=18, *-footprintFlow.json suffix) on a branch — server-tier transactional flow…
Use when authoring or modifying a Datex Studio backend test (configurationTypeId=24, *-backendTest.json suffix) on a branch — mocha test suite with four hook…
Use when investigating the current state of a Datex Studio codebase with read-only inspection — answers questions about existing components, flow code, type…
Use when scaffolding a new Datex Studio component from a documented skeleton — maps a requested type to folder, suffix, configurationTypeId, minimal-valid…
Use when auditing a Datex Studio component file before merge — final gate after authoring or modifying any component (action, function, grid, hub, form,…
Datex Studio platform conventions for component file authoring: file format invariants (configurationTypeId table, file locations and suffixes,…
Datex Studio platform runtime semantics: platform-injected globals (`$flow`, `$datasources`, `$db`, `$shell`, `$frontendFlows`, `$operations`,…
Use when authoring or modifying a Datex Studio editor (configurationTypeId=4, *-editor.json suffix) on a branch — single-entity view/edit screen with embedded…
Use when authoring or modifying a Datex Studio form (configurationTypeId=5, *-form.json suffix) on a branch — transient-input collector, dialog opener, and…
Use when authoring or modifying a Datex Studio grid (configurationTypeId=3, *-grid.json suffix) on a branch — the densest UI component. Owns the pre-author…
Use when auditing a Datex Studio grid configuration before merge or diagnosing grid rendering/filter/sort/toolbar bugs — the mandatory final gate after…
Use after editing or writing any Datex Studio component file — invoked by every creator skill's closer ("After your edit, invoke post-edit-verification"). Runs…
Use when running project-wide lint across a Datex Studio codebase (or a scope subset) — checks 5 categories of cross-component issues that per-file validation…
Use when authoring or modifying a Datex Studio selector (configurationTypeId=7, *-selector.json suffix) on a branch — datasource-backed dropdown /…
Use when authoring or modifying a Datex Studio storage component (configurationTypeId=17, *-storage.json suffix) on a branch — cloud-persisted Mongo storage…
Use when authoring or modifying Datex Studio type definitions (configurationTypeId=22, *-customType.json suffix) on a branch — both interfaces (i_<name>) and…
Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise…
Record browser or Web UI interaction demos as optimized GIFs using the available browser-control workflow, optional Playwright Videos for higher capture frame…
Converts Markdown content into the format required for Dev.to publication, ensuring correct YAML frontmatter, headers, liquid tags, and inline formatting. Use…
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where seams go, make code more testable or more navigable by AI, or when other skills need deep module vocabulary.
Implement work based on a spec or a set of tickets.
Convert markdown plans into beads with dependencies using br CLI. Use when creating task graphs, polishing beads before implementation, or bridging planning to…
GitHub CLI - manage repositories, issues, pull requests, actions, releases, and more from the command line.