smithery/chad3814

Project Conventions

Project structure, git workflow, and environment configuration standards. Use this when organizing files, managing dependencies, setting environment variables, or following version control practices. Maintains consistency across the video generation service.

Installation

$ npx skills add smithery/chad3814 --skill project-conventions

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/chad3814.

npx skills add smithery/chad3814

Browse all from smithery/chad3814

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,869 B
  • docs SUMMARY.md 285 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Project Conventions

This Skill provides Claude Code with specific guidance on how it should handle global conventions.

When to use this skill:

  • Organizing file structure in src/ or server/ directories
  • Managing environment variables and configuration
  • Creating feature branches and commit messages
  • Adding or updating npm dependencies
  • Setting up Docker configuration or secrets
  • Documenting setup instructions in README

Instructions

  • Consistent Project Structure: Organize files and directories in a predictable, logical structure that team members can navigate easily
  • 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 (unit tests, integration tests, etc.)
  • 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