- Home
- Skills
- Agents & Orchestration
- Fitness App Development Toolkit — Six Agent Skills
Works with the AI Agents you already use
Fitness App Development Toolkit — Six Agent Skills
A specialized toolkit for building React/Supabase fitness apps with evidence-based training logic and mobile-first UI.
$10
Fitness App Development Toolkit — Six Agent Skills
Example session with this skill installed
I'm building a React + TypeScript fitness app with Supabase.
Help me implement a workout tracking feature where users can:
- Create reusable workout templates
- Schedule workouts on a calendar
- Record actual sets, reps, and weights
- View previous performance
Follow mobile-first design principles, preserve workout history, and include appropriate validation and tests.
- Read your context and instructions
- Compiled the fitness app development
Summary
Implemented design for a mobile-first workout tracking feature using the Fitness App Development Toolkit.
The solution combines workout domain rules, Supabase database practices, mobile UI guidance, and QA checks.
Deliverables
| Component | Implementation |
|---|---|
| Workout templates | Reusable exercise collections |
| Calendar | Scheduled workout snapshots |
| Workout sessions | Separate planned and actual performance |
| History | Completed sessions remain unchanged |
| Supabase | Relational schema with user-scoped RLS |
| Mobile UI | Large inputs, bottom sheets, responsive layout |
| Testing | Validation, history integrity, regression cases |
Example: Workout data model
type WorkoutSet = {
id: string;
exerciseId: string;
setNumber: number;
reps: number | null;
weightKg: number | null;
completed: boolean;
};
type WorkoutSession = {
id: string;
userId: string;
scheduledWorkoutId: string | null;
startedAt: string;
completedAt: string | null;
sets: WorkoutSet[];
};
Critical data integrity rules
- Editing a workout template must not silently rewrite completed sessions.
- Planned sets and actual recorded performance must be stored separately.
- Users must only access their own session records through Supabase RLS.
- Quick completion must not fabricate exercise performance.
- Historical workouts must remain available after template changes.
Mobile UX requirements
- Design for 390px screens first.
- Use large numeric inputs for sets, reps, and weights.
- Display previous performance for reference.
- Provide clear workout completion controls.
- Ensure forms remain accessible on narrow screens.
Validation and testing
npm run lint
npm run typecheck
npm test
npm run build
These commands are a proposed validation workflow and should only be reported as passed after execution.
Next steps: Implement the schema migrations, application components, data-access logic, and regression tests in the buyer's repository.
Connects securely to your tools. The creator never sees your data.
About this skill
Building a fitness or workout tracking application requires managing complex domain rules, exercise taxonomies, and high-performance mobile interfaces. Most development attempts fail when workout history accidentally mutates or training logic becomes scattered across React components.
This toolkit provides a structured development environment for building evidence-grounded fitness apps. It coordinates six specialized skills to handle exercise library management, training-domain heuristics, workout engine logic, mobile UI design, Supabase database architecture, and automated QA.
What it does
- Exercise Library Management handles imports, normalization, muscle maps, and licensing-aware ingestion.
- Training Engine Implementation applies evidence-based rules for strength, hypertrophy, and hockey-specific performance.
- Workout Logic Enforcement manages the lifecycle of templates, programs, scheduled snapshots, and historical sessions.
- Mobile-First UI Design focuses on one-thumb workflows, bottom sheets, and accessible workout tracking interfaces.
- Database Architecture implements Supabase schema migrations, RLS policies, and data integrity for historical records.
- Automated QA runs mobile-specific smoke tests, accessibility checks, and regression testing for fitness logic.
How it works
- Identify the domain by choosing the relevant skill for your current task, such as database schema or UI design.
- Review project architecture to ensure alignment with existing TypeScript/React and Supabase structures.
- Execute domain logic by following specific guardrails, such as preserving historical data integrity during template edits.
- Verify with QA using automated checks and mobile viewport inspections to ensure feature stability.
Frameworks & tools
Specifically designed for React, TypeScript, and Supabase (Postgres). It utilizes Zod for domain validation and is optimized for mobile-first viewports (375px to 430px).
Why this beats prompting it yourself
Generic prompts often ignore the "historical mutation" trap where deleting a workout template accidentally erases a user's past progress. This skill enforces strict data invariants and professional training heuristics that generic models lack.
Use cases
- Building an exercise library with complex muscle-group taxonomies and SVG maps.
- Implementing a deterministic workout generator that respects equipment and hockey-season constraints.
- Designing a mobile workout tracker with large numeric inputs for high-intensity training.
- Designing Supabase RLS policies for anonymous user identity and private fitness data.
Known limitations
Does not include executable code or a pre-built app. Requires a React/Supabase environment. Domain rules are focused on strength, hypertrophy, and hockey.
- These skills provide agent instructions, not executable software or a completed fitness application.
- Originally designed for a specific React/TypeScript/Supabase fitness project; adaptation may be required for other stacks.
- Some instructions reference external project documentation that is not included in the ZIP.
- Database operations require an appropriately configured Supabase project and credentials.
- The toolkit does not independently provide exercise data, licensed media, live fitness APIs, or medical advice.
- Automated testing depends on the target repository's available scripts and test infrastructure.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 8 days ago
Requires
Permissions
File Scopes
The toolkit needs read access to project files to inspect architecture and requirements. Write access is needed when implementing features, migrations, or tests. Shell access supports builds and validation commands. Database credentials and network access are optional and only required for project-specific integrations. Never expose private keys or secrets.