Global Conventions
Your approach to handling global conventions. Use this skill when working on files where global conventions comes into play.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install jaypaulb-canvusapi-llmdemo-global-conventions
Repository
Skill path: .claude/skills/global-conventions
Your approach to handling global conventions. Use this skill when working on files where global conventions comes into play.
Open repositoryBest for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: jaypaulb.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install Global Conventions into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/jaypaulb/CanvusAPI-LLMDemo before adding Global Conventions to shared team environments
- Use Global Conventions for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- name: Global Conventions description: Your approach to handling global conventions. Use this skill when working on files where global conventions comes into play. --- # Global Conventions This Skill provides Claude Code with specific guidance on how to adhere to coding standards as they relate to how it should handle global conventions. ## Instructions For details, refer to the information provided in this file: [global conventions](../../../agent-os/standards/global/conventions.md) --- ## Referenced Files > The following files are referenced in this skill and included for context. ### ../../../agent-os/standards/global/conventions.md ```markdown ## General development conventions - **Consistent Project Structure**: Organize files and directories in a predictable, logical structure that team members can navigate easily. Structure should reflect the compositional hierarchy (atoms → molecules → organisms → pages). See `atomic-design.md` - **Clear Documentation**: Maintain up-to-date README files with setup instructions, architecture overview, and contribution guidelines - **Version Control Best Practices**: Use clear commit messages, feature branches, and meaningful pull/merge requests with descriptions - **Environment Configuration**: Use environment variables for configuration; never commit secrets or API keys to version control - **Dependency Management**: Keep dependencies up-to-date and minimal; document why major dependencies are used - **Code Review Process**: Establish a consistent code review process with clear expectations for reviewers and authors - **Testing Requirements**: Define what level of testing is required before merging. Testing approach should match compositional level—unit tests for atoms/molecules, integration tests for organisms, e2e for pages. See `atomic-design.md` - **Feature Flags**: Use feature flags for incomplete features rather than long-lived feature branches - **Changelog Maintenance**: Keep a changelog or release notes to track significant changes and improvements ```