OmexIT/skills/repo-conventions
skills/repo-conventions/SKILL.md
--- name: repo-conventions description: Repository-specific engineering conventions: architecture notes, API style, testing approach, and deployment/release norms. Applies automatically when working in this repo. user-invocable: false --- # Repo conventions Update the files in `references/` to match this repository's standards. When working in this repo, follow these rules unless the user explicitly says otherwise: - Prefer existing patterns over introducing new abstractions. - Match naming,
$ install --global
skillsauthnpx skillsauth add OmexIT/claude-skills-pack skills/repo-conventionsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 23, 2026, 8:13 PM182.4s4 files scanned
SKILL.md
- name:
- repo-conventions
- description:
- Repository-specific engineering conventions: architecture notes, API style, testing approach, and deployment/release norms. Applies automatically when working in this repo.
- user-invocable:
- false
Repo conventions
Update the files in references/ to match this repository's standards.
When working in this repo, follow these rules unless the user explicitly says otherwise:
- Prefer existing patterns over introducing new abstractions.
- Match naming, folder structure, and error-handling conventions already in use.
- When unsure, propose 1-2 options and ask which matches the team's preference.
- Check for existing utilities before creating new ones — duplication is a common source of inconsistency.
How to customize these references
Each reference file covers a specific area. Fill them in with your team's actual conventions:
references/architecture.md— System structure, module boundaries, dependency rulesreferences/api-style.md— Endpoint naming, request/response conventions, error formatreferences/testing.md— Test organization, naming, coverage expectations, fixtures
If your team has additional convention areas (e.g., database migrations, feature flags, logging), create additional reference files and list them here.
Quality bar for conventions
Good convention docs are:
- Specific enough to resolve ambiguity ("use camelCase for JS, snake_case for Python" not "be consistent")
- Short enough to actually read (aim for 1-2 pages per reference)
- Maintained when conventions change (stale conventions are worse than no conventions)
- Accompanied by examples from the actual codebase
References
references/architecture.mdreferences/api-style.mdreferences/testing.md
Related Skills
OmexIT/verify-impl
tools
VerifiedTrustedCommunity
Use this skill to verify a completed implementation through live testing — API calls, database state checks, and UI automation with Playwright. Triggers include: "test the implementation", "verify this works", "run API tests", "check the database", "test the UI", "end-to-end verify", "smoke test", "sanity check the implementation", "manually test", or any time an implementation needs post-build validation beyond unit tests. Also triggered automatically by spec-to-impl during the integration review phase. Use this when you want real evidence the system works — not just that tests compile. Can consume a pre-generated e2e/test-plan.yaml from spec-to-impl for fully automated test execution.
13SKILL.mdUpdated Apr 23, 2026
OmexIT/skills/ux-review
development
VerifiedTrustedCommunity
--- name: ux-review description: Evaluate a UI/UX design or implementation using heuristic analysis, accessibility audit, and cognitive walkthrough. Triggers: "UX review", "usability review", "heuristic evaluation", "accessibility audit", "is this usable". argument-hint: "[feature / screen / URL / mockup]" effort: high --- # UX review ## What I'll do Evaluate a design or implementation for usability, accessibility, and user experience quality using established heuristic frameworks. ## Inputs
13SKILL.mdUpdated Apr 23, 2026
OmexIT/skills/user-flow
development
VerifiedTrustedCommunity
--- name: user-flow description: Map user journeys through a feature or product, identifying key paths, decision points, friction, error states, and edge cases. Triggers: "user flow", "user journey", "flow diagram", "happy path", "user path". argument-hint: "[feature / user goal]" effort: medium --- # User flow ## What I'll do Map the complete user journey for a feature — from entry point through completion — including happy paths, error states, edge cases, and decision points. > **user-flow
13SKILL.mdUpdated Apr 23, 2026
OmexIT/ui-design
development
VerifiedTrustedCommunity
Use this skill to produce complete UI/UX design artifacts from a specification document or panel analysis. Triggers include: "design the UI for this spec", "create wireframes", "design this panel", "UX design from spec", "generate component specs", "design tokens", "create the UI design for", "design system for", "wireframe this feature", "design a UI", "create a design system", "design this component", "design the layout", "create a style guide", "design a screen", "UI/UX review", "typography system", "color system", "spacing system", "design this feature", "design the dashboard", "design the onboarding", "create a component library", "design review", "audit the design", "improve the UI", "redesign this", "design system documentation", "create design guidelines", "responsive design", "mobile design", "dark mode design", "design the brand", or any time a spec/panel analysis document needs to be transformed into actionable UI/UX deliverables before implementation. Also triggers for standalone design system creation, component design, design reviews, dark mode/responsive variants, and developer handoff — even before code is involved. Orchestrates a multi-agent design team (UX Lead, UI Designer, Component Architect, Accessibility Reviewer, Design System Engineer, Design Reviewer) in parallel waves. Outputs feed directly into spec-to-impl's FE agent and figma-to-code.
13SKILL.mdUpdated Apr 23, 2026