Skip to content
TrustedSkillsbeta
Back to all skills

Cc Skill Project Guidelines Example

Checked
davila7·vlatest·frontend·MIT

Provides clear, concise guidance on project guidelines based on davila7's established frontend coding standards.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add davila7/claude-code-templates --skill cc-skill-project-guidelines-example -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

davila7

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned davila7/claude-code-templates at 79182c51fb.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
79182c51fb
Manifest
cli-tool/components/skills/development/cc-skill-project-guidelines-example/SKILL.md
Scanned
1 file, 329 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

cc-skill-project-guidelines-example

What it does

This skill provides structured project guidelines specifically designed for AI coding agents to ensure consistent output and adherence to architectural standards. It acts as a reference framework that directs the agent on how to approach, organize, and execute development tasks within a specific codebase context.

When to use it

  • Onboarding new agents: Deploy when introducing an AI tool to a legacy codebase or a project with strict style guides to prevent drift.
  • Enforcing architecture: Use during feature implementation to ensure the agent respects existing design patterns and folder structures.
  • Standardizing documentation: Activate when generating commit messages, changelogs, or inline comments to maintain uniformity across the team.
  • Refactoring safety: Apply before large-scale refactoring tasks to guarantee the agent understands constraints and dependencies.

Key capabilities

  • Defines clear project structure and file organization rules.
  • Specifies coding standards, naming conventions, and language-specific best practices.
  • Outlines expected output formats for code generation and documentation.
  • Sets boundaries for acceptable changes and integration protocols.

Example prompts

  • "Review the attached project guidelines before generating code for the new authentication module."
  • "Refactor this function according to the project guidelines regarding error handling and logging."
  • "Generate a pull request description that aligns with the documentation standards defined in these guidelines."

Tips & gotchas

Ensure the project guidelines file is accessible within the agent's context window or knowledge base before initiating complex tasks. This skill relies on the accuracy of the provided guidelines; outdated rules may lead to incorrect code generation, so verify them against current team standards.