cc-skill-project-guidelines-example
Apply Project Coding Guidelines
Teams need consistent architecture, testing, and deployment patterns for full-stack AI applications. This skill provides a reusable project guideline template for Claude, Codex, and Claude Code.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "cc-skill-project-guidelines-example" from https://skillstore.io/skills/sickn33-cc-skill-project-guidelines-example.md and its manifest at https://skillstore.io/api/skills/sickn33-cc-skill-project-guidelines-example/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "cc-skill-project-guidelines-example". Review a frontend API helper.
Expected outcome:
- Confirms the helper uses the shared response shape.
- Checks error handling and loading state expectations.
- Lists missing tests for failed and successful responses.
Using "cc-skill-project-guidelines-example". Plan backend tests for a new endpoint.
Expected outcome:
- Identifies pytest coverage for success, validation errors, and authentication failures.
- Recommends fixtures that match the documented FastAPI test pattern.
- Adds coverage expectations before implementation starts.
Using "cc-skill-project-guidelines-example". Prepare a deployment review.
Expected outcome:
- Checks frontend build status, backend test status, and migration readiness.
- Verifies environment variables are documented without real secrets.
- Flags deployment commands that need explicit approval.
Security Audit
SafeMost static findings are false positives caused by Markdown code fences, inline command examples, placeholder URLs, and placeholder environment variable names. No evidence of executable hooks, hidden network exfiltration, prompt injection, or real credentials was found in SKILL.md. The skill still contains deployment and secret placeholder examples, so authors should label them clearly as illustrative.
Risk Factors
⚙️ External commands (31)
🌐 Network access (6)
🔑 Env variables (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-cc-skill-project-guidelines-example/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-cc-skill-project-guidelines-example?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-cc-skill-project-guidelines-example?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-cc-skill-project-guidelines-example/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-cc-skill-project-guidelines-example.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
affaan-m. (2026). cc-skill-project-guidelines-example security audit report (audit version 4) [Author version 1.0]. Skillstore. https://skillstore.io/skills/sickn33-cc-skill-project-guidelines-example/audits/4BibTeX citation
@techreport{affaan-m-sickn33-cc-skill-project-guidelines-example-2026,
author = {affaan-m},
title = {cc-skill-project-guidelines-example security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/sickn33-cc-skill-project-guidelines-example/audits/4},
note = {Author version 1.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "cc-skill-project-guidelines-example security audit report (audit version 4)"
version: "1.0"
type: report
authors:
- name: "affaan-m"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/sickn33-cc-skill-project-guidelines-example/audits/4"
identifiers:
- type: other
value: "skillstore:sickn33-cc-skill-project-guidelines-example:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Onboard New Developers
Give new engineers a concise map of architecture, file layout, testing rules, and coding standards.
Standardize Backend Work
Help backend contributors align API responses, Pydantic models, pytest structure, and error handling.
Prepare Releases
Review build checks, test coverage, environment variables, migrations, and Cloud Run deployment steps.
Try These Prompts
Use this skill to summarize the project standards and list the first files I should inspect.
Review my new endpoint against the API response and testing patterns from this skill.
Create a test plan for this feature using the backend and frontend testing requirements in this skill.
Audit this pull request for architecture, deployment readiness, environment variable handling, and rule violations from this skill.
Best Practices
- Use the skill as a checklist before changing shared architecture or deployment workflows.
- Keep project-specific values separate from the example placeholders in the skill.
- Ask the assistant to cite which guideline supports each review comment.
Avoid
- Do not run deployment commands unless the user explicitly requests deployment.
- Do not copy placeholder secrets into real environment files.
- Do not treat the example architecture as mandatory for unrelated projects.