Run any Skill in Manus with one click

implement-feature

Stars1

Forks0

UpdatedJune 9, 2026 at 01:37

Implement a new feature or component following the conventions of this monorepo. Use when the user asks to build something new in the staff/public UIs, shared packages, or api. Strongly prefer using Ant Design for UI work and the shared @repo/ui library.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

simnova

simnova/agent-playground

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	implement-feature
description	Implement a new feature or component following the conventions of this monorepo. Use when the user asks to build something new in the staff/public UIs, shared packages, or api. Strongly prefer using Ant Design for UI work and the shared @repo/ui library.

Implement Feature Skill

Follow this process when asked to add new functionality.

1. Understand the Request

Clarify scope: Which app(s)? (staff, public, api, packages/ui, etc.)
Check existing patterns by reading similar code.
Look for relevant skills (e.g. review-component, add-ui-component) and AGENTS.md.

2. Design

For UI work: Use antd as primary. Wrap with AntdProvider theming. Reuse or extend from @repo/ui when possible.
For backend: Follow the Hono + Apollo patterns in apps/api.
For shared code: Put reusable logic/types in the appropriate package.
Prefer TypeScript, strict config from @repo/config-typescript.
Consider both staff and public UIs — share what makes sense.

3. Implementation Steps

Plan the changes (files to create/edit).
Implement incrementally, using search_replace or write.
Keep components focused and typed.
Add necessary GraphQL schema/resolvers/mutations if touching the backend.
Update any relevant documentation or AGENTS.md notes.

4. Quality

Run biome check . and fix issues.
Run tsgo --noEmit (or the project's check-types) and fix.
If UI, make sure it works with the current theming (different primary colors for staff vs public).
Consider accessibility and responsive behavior.

5. Review & Test

Use the review-component skill (or thorough-reviewer persona) on the changes.
Provide a summary of what was built and how to test it.

Always prefer small, reviewable changes. Reference specific files and the monorepo structure.

Backend calc / pure module hygiene (cross-skill, per agent-evaluator): When touching portable engines (e.g. calculateDepositAllocation or similar in api/src/graphql/*), after the main implementation:

Verify the named export.
Run a live sample call with realistic BankBuckets seed data (percentAlloc + maxAmount + spillOverOrder buckets; deposit sized to hit caps + trigger waterfall + remainder handling). Assert no NaN, correct allocated/capped/spillOverBucketUsed, and projected values. Use the project's runner (bun for api .ts). Record "sample verified" in your todo/hand-off. This directly prevents the class of runtime NaN bugs that block server apply/persist even when client preview works.

More from this repository

same repository

add-antd-component

simnova/agent-playground

Add a new Ant Design based component or page feature to the staff or public Vite apps, or extend the shared @repo/ui library. Use when the user wants to introduce new UI elements using antd as the primary library.

2026-06-081

add-new-vite-app

simnova/agent-playground

Scaffold a new Vite + React + TypeScript app in this Turborepo (e.g. a third UI besides staff and public). Use when the user wants to add another frontend that will also connect to the shared api backend.

2026-06-081

add-ui-component

simnova/agent-playground

Create a new reusable UI component or page feature in one of the Vite UIs (staff or public), or extend the shared @repo/ui library. Use when the user wants to add a new button, form, page section, or feature using Ant Design as the primary library.

2026-06-081

apollo-client

simnova/agent-playground

Guide for building React applications with Apollo Client in the staff and public Vite apps. Use when: (1) setting up or configuring Apollo Client in apps/staff or apps/public, (2) writing GraphQL queries or mutations with hooks (useQuery, useMutation), (3) configuring caching, cache policies, or optimistic UI, (4) managing local state or error handling in the UIs that connect to the shared apps/api backend, (5) troubleshooting Apollo Client errors, performance, or integration with Ant Design components. Always coordinate with the backend schema in apps/api and use the shared @repo/ui + AntdProvider theming. Prefer patterns that work for both staff (internal) and public (customer-facing) experiences.

2026-06-081

apollo-connectors

simnova/agent-playground

Guide for writing Apollo Connectors schemas to integrate REST APIs into GraphQL. Use this skill when: (1) connecting REST services to the GraphQL backend in apps/api, (2) using @source and @connect directives, (3) implementing entity resolvers with batching from external APIs. In this monorepo, use to extend the Hono/Apollo API without duplicating logic. The staff/public UIs can then query unified data. Coordinate with graphql-schema, update-graphql, apollo-server. Test via portless https://api.localhost/graphql.

2026-06-081

apollo-federation

simnova/agent-playground

Guide for authoring Apollo Federation subgraph schemas with entities, sharing, and cross-subgraph resolution. Use this skill when: (1) creating or evolving federated schemas for the backend (future split of apps/api or new subgraphs), (2) defining entities with @key, (3) using @shareable, @external, @requires, @provides, @override, (4) troubleshooting composition errors. In this monorepo, start with the single server in apps/api but prepare for federation. Coordinate with graphql-schema, update-graphql, rover. The UIs in staff/public would query the supergraph.

2026-06-081

name	implement-feature
description	Implement a new feature or component following the conventions of this monorepo. Use when the user asks to build something new in the staff/public UIs, shared packages, or api. Strongly prefer using Ant Design for UI work and the shared @repo/ui library.

Implement Feature Skill

Follow this process when asked to add new functionality.

1. Understand the Request

Clarify scope: Which app(s)? (staff, public, api, packages/ui, etc.)
Check existing patterns by reading similar code.
Look for relevant skills (e.g. review-component, add-ui-component) and AGENTS.md.

2. Design

For UI work: Use antd as primary. Wrap with AntdProvider theming. Reuse or extend from @repo/ui when possible.
For backend: Follow the Hono + Apollo patterns in apps/api.
For shared code: Put reusable logic/types in the appropriate package.
Prefer TypeScript, strict config from @repo/config-typescript.
Consider both staff and public UIs — share what makes sense.

3. Implementation Steps

Plan the changes (files to create/edit).
Implement incrementally, using search_replace or write.
Keep components focused and typed.
Add necessary GraphQL schema/resolvers/mutations if touching the backend.
Update any relevant documentation or AGENTS.md notes.

4. Quality

Run biome check . and fix issues.
Run tsgo --noEmit (or the project's check-types) and fix.
If UI, make sure it works with the current theming (different primary colors for staff vs public).
Consider accessibility and responsive behavior.

5. Review & Test

Use the review-component skill (or thorough-reviewer persona) on the changes.
Provide a summary of what was built and how to test it.

Always prefer small, reviewable changes. Reference specific files and the monorepo structure.

Verify the named export.
Run a live sample call with realistic BankBuckets seed data (percentAlloc + maxAmount + spillOverOrder buckets; deposit sized to hit caps + trigger waterfall + remainder handling). Assert no NaN, correct allocated/capped/spillOverBucketUsed, and projected values. Use the project's runner (bun for api .ts). Record "sample verified" in your todo/hand-off. This directly prevents the class of runtime NaN bugs that block server apply/persist even when client preview works.