conventions
Apply Project Coding Conventions
Codebases drift when contributors apply different style choices. This skill loads project conventions so Claude, Codex, and Claude Code can follow shared standards.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "conventions" from https://skillstore.io/skills/clouder0-conventions.md and its manifest at https://skillstore.io/api/skills/clouder0-conventions/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 "conventions". Review a new service module for convention fit.
Expected outcome:
- Naming follows the repository pattern for service classes.
- The file belongs with related domain services, not shared utilities.
- Add a focused unit test for the documented error path.
Using "conventions". Plan a refactor before editing a feature area.
Expected outcome:
- Keep public function names stable unless the convention requires a rename.
- Move helper logic near the feature owner module.
- Update documentation if the user-facing behavior changes.
Security Audit
SafeStatic analysis reported no suspicious patterns in the single prompt file. Manual review found a read-only coding conventions skill with no executable code, network behavior, secret handling, or prompt-injection attempt.
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/clouder0-conventions/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/clouder0-conventions?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/clouder0-conventions?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/clouder0-conventions/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/clouder0-conventions.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
Clouder0. (2026). conventions security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/clouder0-conventions/audits/8BibTeX citation
@techreport{clouder0-clouder0-conventions-2026,
author = {Clouder0},
title = {conventions security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/clouder0-conventions/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "conventions security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "Clouder0"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/clouder0-conventions/audits/8"
identifiers:
- type: other
value: "skillstore:clouder0-conventions:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Standardize New Features
Apply repository naming, file layout, and testing expectations before generating new code.
Review Pull Requests
Check proposed changes against shared style, error handling, documentation, and test conventions.
Guide Refactoring Work
Keep refactors aligned with existing project standards while improving structure or readability.
Try These Prompts
Read the project coding conventions and summarize the rules I should follow for this task.
Use the project coding conventions while implementing this change. Call out any convention that affects your approach.
Review this change against the project coding conventions. Focus on naming, file organization, tests, errors, and documentation.
Plan this refactor using the project coding conventions. Identify standards that should shape the file layout, tests, and error handling.
Best Practices
- Load the conventions before generating or reviewing code.
- Ask for specific convention checks when reviewing a diff.
- Update the referenced conventions file when project standards change.
Avoid
- Using the skill without the conventions file available.
- Treating suggestions as a substitute for tests or linters.
- Applying conventions from another repository without checking local rules.