Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
This collection provides targeted skill sets for developers managing diverse tech stacks. It streamlines the transition between frontend and backend contexts by offering specialized guidance for specific frameworks and architectural patterns.
Engineers can use these skills to author Architecture Decision Records, evaluate technology trade-offs, and implement complex state management or routing configurations in enterprise applications.
WHO IT'S FOR
Full-stack developers
accelerating feature delivery across diverse tech stacks
Technical leads / architects
authoring ADRs and designing system architectures
Backend engineers
designing REST or GraphQL API specifications
Enterprise frontend developers
implementing NgRx state and Angular standalone components
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Use the debugging-wizard skill to investigate this single reproducible failure. Start from the supplied reproduction steps, complete error message or stack trace, relevant logs, and referenced code paths. Test one hypothesis at a time, then give me a concise first result containing the most likely root cause, supporting evidence, a proposed fix, and a regression-prevention test. Do not modify production systems.
Use the architecture-designer skill to draft a high-level architecture for the system described below. Summarize the functional requirements, non-functional requirements, and constraints; produce a Mermaid diagram; compare the main trade-offs; and write one ADR for the most important decision. Clearly list risks, mitigations, and any requirements that still need stakeholder confirmation.
Use the vue-expert skill to draft one small Vue 3 component for the behavior described below. Use Composition API, <script setup>, and type-safe TypeScript props. Include the component code, a brief explanation of the reactivity choices, and a focused Vue Test Utils/Vitest test. Identify any project-specific dependencies or assumptions instead of inventing them.