convention-learner
Discover and Apply .NET Project Conventions
Inconsistent naming and structure make existing .NET projects harder to extend and review. This skill guides evidence-based convention discovery and applies findings to code suggestions.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "convention-learner" from https://skillstore.io/skills/codewithmukesh-convention-learner.md and its manifest at https://skillstore.io/api/skills/codewithmukesh-convention-learner/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 "convention-learner". Summarize conventions from a supplied sample of five handlers and existing project settings.
Expected outcome:
- Naming: All five inspected handlers use the Handler suffix.
- Modifiers: All five sampled handlers are internal and sealed; confirm other modules before making this a project-wide rule.
- Configuration: The supplied settings require file-scoped namespaces.
- Recommendation: Document these findings and inspect additional layers before enforcing inferred rules.
Using "convention-learner". Review a public handler when twelve comparable handlers are internal and sealed.
Expected outcome:
- Deviation: The new handler is public, while all twelve comparable handlers are internal and sealed.
- Suggested change: Match the existing modifiers unless this handler has a documented accessibility requirement.
- Follow-up: Record the confirmed convention in team documentation after review.
Security Audit
SafeAll 58 static findings are false positives from Markdown formatting, C# examples, and an illustrative quality table. No evidence found of malicious execution, exfiltration, or prompt injection in SKILL.md. The skill describes project analysis through MCP tools and file reads, with suggested convention documentation and configuration changes.
Risk Factors
โ๏ธ External commands (50)
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/codewithmukesh-convention-learner/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/codewithmukesh-convention-learner?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/codewithmukesh-convention-learner?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/codewithmukesh-convention-learner/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/codewithmukesh-convention-learner.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
codewithmukesh. (2026). convention-learner security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/codewithmukesh-convention-learner/audits/1BibTeX citation
@techreport{codewithmukesh-codewithmukesh-convention-learner-2026,
author = {codewithmukesh},
title = {convention-learner security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/codewithmukesh-convention-learner/audits/1},
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: "convention-learner security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "codewithmukesh"
date-released: "2026-10-31"
url: "https://skillstore.io/skills/codewithmukesh-convention-learner/audits/1"
identifiers:
- type: other
value: "skillstore:codewithmukesh-convention-learner:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Understand an Existing Codebase
Inspect representative types, folder layouts, and configuration to summarize conventions before implementing a first change.
Review Convention Deviations
Compare changed handlers and DTOs against observed project patterns, distinguishing explicit rules from inferred preferences.
Document Team Standards
Turn repeated code patterns and quality findings into proposed convention documentation and EditorConfig settings.
Try These Prompts
Inspect this .NET project and summarize naming, folder organization, and coding style. Cite representative files and distinguish confirmed patterns from uncertain observations.
Review existing features before planning [feature]. Identify matching folders, handler modifiers, DTO styles, and configuration rules. Propose an implementation outline without editing files.
Compare the changed files with representative project code and explicit configuration. Report convention deviations with evidence and suggested fixes. Do not treat exceptions as universal rules.
Analyze representative layers and available anti-pattern results. Separate explicit rules from inferred patterns, compare supplied historical counts, and propose CLAUDE.md and EditorConfig changes for approval.
Best Practices
- Inspect several representative files across layers before documenting an inferred convention.
- Give explicit .editorconfig and Directory.Build.props rules precedence over inferred style preferences.
- Review proposed documentation and configuration changes before applying them to the repository.
Avoid
- Imposing generic handler modifiers or folder layouts without examining the existing project.
- Treating a pattern observed in one file as a universal team standard.
- Claiming historical trends or automatic enforcement without the required tools and supporting evidence.
Frequently Asked Questions
Which projects does this skill target?
Does the skill include analysis tools?
Can it enforce conventions automatically?
What happens when existing settings conflict with inferred conventions?
Can it track quality trends across sessions?
Will it rewrite the entire repository?
Developer Details
Author
codewithmukeshLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
79a2b74ba8b6a6a3c05dcf469ad5fe4034b72472
Maintenance freshness
10/31/2026
Usage
0 downloads ยท 0 views
File structure
๐ SKILL.md