A workflow guide for connecting a frontend to an API, a service that lets software exchange data. It covers endpoints, query and mutation hooks, data types, errors, caching, and related implementation choices.
A workflow for placing components reused across several pages of one app. It keeps them together without moving them into a design-system package before reuse across multiple apps is certain.
A review workflow for deciding how a new app or package should be structured. It examines shared boundaries, routing boundaries, and whether something should become part of the design system.
A workflow for reviewing pull requests in the GitHub web interface. It records the visible code changes, review comments, check results, and whether the code was tested locally as separate facts.
A workflow for turning a code change into a plan for staging and committing it. It divides the actual diff—the changes between file versions—into feature, work, and verification units.
A workflow for working on components in a design system, a shared set of interface building blocks. It covers checking the purpose and required inputs before starting.
A workflow for building frontend forms with field validation, submission, server changes, and error, disabled, loading, and success states. A mutation is an operation that changes data on a server or in a database.
A frontend review skill based on Toss Frontend Fundamentals, a set of frontend design principles. It checks whether related components, hooks, types, test data, specifications, and form flows are kept together coherently.
A frontend review for finding unnecessary connections between parts of an application, such as hooks with mixed responsibilities, deeply passed properties, or duplicated code. Props drilling means passing data through several component layers just to reach a deeper component.
A frontend code-review workflow based on guidelines for readable, predictable code with clear relationships between parts. Frontend code is the code that runs in a web browser or app interface.
A workflow for deciding when component logic should stay in a component, move into a custom hook, or become a shared hook. It also provides a self-check for the implementation.
A frontend review for checking whether code behaves in ways that users and other developers can predict. It covers names, return types, side effects, React state, and the meaning of UI elements.
A checklist and workflow for checking frontend changes with formatting, linting, type checking, and a production build. Linting finds common code problems, while type checking catches mismatched data types.
A review checklist based on Toss Frontend Fundamentals, a set of guidelines for readable frontend code. It checks context, naming, conditional rendering, and the flow of JSX, the markup-like syntax often used in React.
A required workflow for frontend work based on Jira tasks, Figma designs, photos, and other evidence. It covers creating or checking a Jira task, writing a specification, implementing the work, improving it, and verifying the result.
A maintenance workflow for checking whether a set of coding-agent skills is still complete and up to date. It looks for missing verification coverage, outdated references, and missing checks.
A workflow for implementing and checking pages or routes in the Dongchimi app using Jira tasks, Figma designs, specifications, and generated references.
A workflow for monitoring status changes across Jira, GitHub pull requests and checks, and Notion boards. It separates changes an agent should report from unimportant notification noise.
A workflow for creating or modifying Turborepo generators, templates, and scaffolding. Turborepo is a tool for managing multiple related projects in one repository.
Skill "verify-agent-docs" from TEAM-DONGCHIMI/DONGCHIMI-CLIENT, covering agent docs verification, purpose, related files, workflow and step 1: diff whitespace 검사.
★not rated 11 1mo agoA39 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: