A collection of Agent Skills Standard and Best Practice for Programming Languages, Frameworks that help our AI Agent follow best practies on frameworks and programming laguages
Enforce universal security protocols for safe, resilient software. Use when implementing authentication, encryption, authorization, input validation, secret management, or any security-sensitive feature across any language or framework.
★not rated 565▲
+4 3d agoASkillSpector: pass43 tokens
originalMIT
Analyze conversation corrections to detect skill gaps and prepare targeted skill-library maintenance tasks. Use after any session with user corrections, rework, or retrospective requests. After finding correction loops, also load +common/common-learning-log to persist mistake entries to AGENTSLEARNING.md.
★not rated 565▲
+4 3d agoASkillSpector: pass59 tokens
originalMIT
Standardizes the creation and evaluation of high-density Agent Skills (Claude, Cursor, Windsurf). Ensures skills achieve high Activation (specificity/completeness) and Implementation (conciseness/actionability) scores. Use when: writing or auditing SKILL.md, improving trigger accuracy, or refactoring skills to reduce…
★not rated 565▲
+4 3d agoASkillSpector: pass75 tokens
originalMIT
Standardize SRS and FRS specifications for technical behavior, interfaces, data contracts, quality constraints, and verification mapping. Use when writing SRS, functional specification, system behavior requirements, API/data contracts, or non-functional thresholds.
★not rated 565▲
+4 3d agoASkillSpector: pass53 tokens
originalMIT
Generate user-facing release notes for the App Store and Google Play from git history (App Store <=4000 chars, Google Play <=500). Use when generating release notes, app store changelog, play store release, or "what's new" text for a mobile app.
★not rated 565▲
+4 3d agoASkillSpector: pass60 tokens
originalMIT
Guides quality-first TDD for new behavior, bug fixes, and test changes. Selects the smallest test layer, proves a distinct regression risk, and runs bounded RED-GREEN-REFACTOR verification.
★not rated 565▲
+4 3d agoASkillSpector: pass46 tokens
originalMIT
Enforce session-cost telemetry and execution-metadata reporting. Use when explicitly invoking getsessioncost, reporting token/cost usage, applying telemetry or cost guidance during a workflow handoff, or writing artifacts/session-cost.md at a workflow terminal state.
★not rated 565▲
+4 3d agoASkillSpector: pass53 tokens
originalMIT
Design distinctive, production-grade frontend UI with bold aesthetic choices. Use when building web components, pages, interfaces, dashboards, or applications in any framework (React, Next.js, Angular, Vue, HTML/CSS).
★not rated 565▲
+4 3d agoASkillSpector: pass47 tokens
originalMIT
Standardizes visual audits, responsive design, and behavioral testing for web apps. Use to verify a web UI fix or cross-browser behavior; defer backend API refactors, Playwright installation/tooling setup, and Appium/mobile automation.
★not rated 565▲
+4 3d agoASkillSpector: pass52 tokens
originalMIT
Rules for writing concise, token-efficient workflow and skill files. Prevents over-building that requires costly optimization passes. Use when creating or editing workflow files, SKILL.md files, or new skill definitions.
★not rated 565▲
+4 3d agoASkillSpector: pass45 tokens
originalMIT
Drives iOS/Android mobile devices via Appium MCP. Use for verifying mobile bugs, E2E tests, and navigating real device clouds (LambdaTest/BrowserStack).
★not rated 565▲
+4 3d agoASkillSpector: pass44 tokens
originalMIT
Investigate requirements via atomic AC decomposition, actor/permission matrices, and truth-table edge cases; enforce User Story standards (scope fences, platform tags, toggles). Use when writing/reviewing Stories or AC with multi-condition logic, feature toggles, or market variants (VN/MY/SG).
★not rated 565▲
+4 3d agoASkillSpector: pass67 tokens
originalMIT
Trigger only when the user explicitly requests live Jira or Zephyr retrieval, existing-link inspection, linking authored test cases, label updates, or stale-link audits. Do not trigger for analysis-only prompts such as 'Analyze the acceptance criteria for TICK-4521', supplied acceptance criteria, test-case authoring…
★not rated 565▲
+4 3d agoASkillSpector: pass75 tokens
originalMIT
Write or review manual Zephyr test cases with 1-condition-per-TC granularity, ModuleAction on Screen when Condition naming, platform prefix rules, and High/Normal/Low priority classification. Use for test-case authoring and review; defer Jira traceability, linking, and pushing cases to Zephyr.
★not rated 565▲
+4 3d agoASkillSpector: pass69 tokens
originalMIT
Audit test coverage health, gaps, and QE debt for Jira stories or epics. Produces coverageanalysisreport.md with AC-to-TC heatmap, risk scores, and prioritized action plan. Use when assessing coverage percentage, pre-release readiness, sprint readiness, or identifying missing test cases. Do NOT use for TC creation …
★not rated 565▲
+4 3d agoASkillSpector: pass81 tokens
originalMIT
Generate Zephyr test cases from Jira stories: parse acceptance criteria and business rules, impact-analyze existing TCs (update vs. create new), and draft correctly named test cases. Use for AC-to-test generation; defer post-generation Jira linking and manual test-case quality review.
★not rated 565▲
+4 3d agoASkillSpector: pass63 tokens
originalMIT
Ingest a provided design artifact - screenshot, drawio, Mermaid, PlantUML, Excalidraw, slides, PDF, or IaC - into a reviewable fact sheet. Probes for embedded structure before vision, marks per-edge confidence, treats extracted text as data. Use when someone hands over a design to review.
★not rated 565▲
+4 3d agoASkillSpector: pass74 tokens
originalMIT
Select infrastructure components by the constraint each removes: load balancers, caches and invalidation, queues and pub/sub, CDN, API gateway, rate limiting, consistent hashing. Use when choosing cache, queue, replica, or edge layers; defer engine tuning to the database category.
★not rated 565▲
+4 3d agoASkillSpector: pass61 tokens
originalMIT
Answer classic system design problems as constraint-to-solution sketches and coach interview practice: URL shortener, rate limiter, news feed, chat, notification, autocomplete, crawler, unique id. Use for interview practice or naming the closest known shape for a new problem.
★not rated 565▲
+4 3d agoASkillSpector: pass58 tokens
originalMIT
Select how services talk: REST, gRPC, GraphQL, WebSocket, SSE, or webhook per hop, sync versus async per flow, service discovery mode, and DNS/edge routing. Use when choosing a protocol or API paradigm; defer REST contract detail (status codes, pagination, OpenAPI) to common-api-design.
★not rated 565▲
+4 3d agoASkillSpector: pass71 tokens
originalMIT
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: