Automated summary
This skill defines directory structure, naming, and dependency rules for .NET projects using the dotcore (shared libraries) and dotapps (runnable apps) architecture.
Strengths
- Clearly separates reusable libraries from applications
- Prevents circular dependencies between projects
- Enforces consistent naming conventions
- Facilitates maintainability and scalability
Limitations
- Only applicable to projects following this specific architecture
- Requires discipline to avoid rule violations
- May be overly rigid for small projects without sharing needs
When working on a .NET project with multiple applications sharing common libraries and you want to follow a standardized architecture.
For a standalone single application or a project that does not need a clean separation between shared code and apps.
Security analysis
SafeThe skill provides only project layout and naming guidelines for a .NET codebase. It includes standard build and run commands (dotnet build, dotnet run) but no network access, file deletion, or exfiltration instructions. No obfuscation or disabling of safety features. All actions are legitimate development tasks.
No concerns found
How this analysis is madeExamples
I need to create a new shared library for logging that will be used by multiple apps. Where should I put it and what should I name it according to the dotcore/dotapps architecture?I'm adding a new feature to the Cli app and need to use classes from DotCore.Utils. What is the correct project reference path to add in the Cli.csproj file?I want to add unit tests for DotCore.Foundations. Where should the test project live and what should its project reference look like?name: dot description: When working on dotcore (shared .NET libs = public class libraries = pycore counterpart) or dotapps (runnable apps), follow layout, naming, and dependency rules. All shared libraries live in dotcore; apps reference only dotcore.
Dot Stack Skill (dotcore + dotapps)
Use this skill when editing or adding code under dotcore/ or dotapps/.
- dotcore = .NET public class libraries (公共类库) = counterpart of pycore. All shared libraries used by more than one app (DotCore.Foundations, DotCore.Common, DotCore.Utils, DotCore.Infrastructure, DotCore.UIInspect, DotCore.UITheme, etc.) live here.
- dotapps = runnable applications; they reference dotcore and, when needed, their own sub-app characteristic library (子APP的特征类库) under dotapps/<App>/ (e.g. dotapps/d3check/D3CheckCore/). No app-to-app references.
Canonical spec: development-guides/DOT_ARCHITECTURE.md. Cursor rule: .cursor/rules/dot.mdc. UI (WPF/MAUI/Blazor/Avalonia): canonical spec development-guides/DOT_UI_PROJECT_SPECIFICATION.md, .cursor/rules/dot-ui.mdc. Progress and pycore↔dotcore mapping: dotcore/DOT_PUBLIC_LIBRARY_PROGRESS.md.
When to Use
- Editing or adding code under
dotcore/(any DotCore.* project or tests). - Editing or adding code under
dotapps/(SimpleUi, Cli, CallModule, d3check, or any new app). - Adding a new shared library (as a new DotCore.* under dotcore) or a new app (under dotapps).
- Choosing where to put types, utilities, or config used by multiple apps (dotcore, not dotapps).
Instructions
1. Layout: all shared libs in dotcore, apps in dotapps
- dotcore/ = shared class libraries only. Every subfolder is one library (e.g.
DotCore.Foundations). All code used by more than one app, or shared infrastructure, belongs here. Sub-app characteristic libs (子APP的特征类库) belong under dotapps/<App>/ (e.g. dotapps/d3check/D3CheckCore/), not in dotcore. No runnable apps under dotcore. - dotapps/ = runnable applications only. Every subfolder is one app (e.g.
SimpleUi,Cli,CallModule,d3check). Apps reference dotcore and, when needed, a project under the same app (e.g. d3check → D3CheckCore); no app-to-app project references. - Tests live under
dotcore/tests/(e.g.DotCore.Foundations.Tests).
2. Naming and code language
- Language: All code, comments, and user-facing strings in English. ASCII only in source code.
- Libraries: Folder and project name
DotCore.<Name>(e.g.DotCore.Utils). NamespaceDotCore.*. - Apps: Folder and assembly name match (e.g.
SimpleUi). Root namespace DotApps.<AppName> (e.g.DotApps.SimpleUi).
3. Dependencies
- Direction: Apps → Libraries only. Libraries do not reference apps. Libraries may reference other libraries only in a DAG (no cycles).
- DotCore.Foundations: No project refs; BCL/minimal NuGet only.
- DotCore.Common: Foundations only.
- DotCore.Utils / DotCore.Infrastructure: Foundations + Common (and optional third-party).
- DotCore.UIInspect: Optional third-party (e.g. FlaUI) only; no dotcore project refs if not needed.
- Apps: Reference only the
DotCore.*projects they need (e.g. Cli uses Foundations, Common, Utils; SimpleUi uses UIInspect).
4. Project reference paths
- From app (dotapps/<AppName>/):
..\..\dotcore\DotCore.<Name>\DotCore.<Name>.csproj - From library (dotcore/):
..\DotCore.<Name>\DotCore.<Name>.csproj - From test (dotcore/tests/...):
..\..\DotCore.<Name>\DotCore.<Name>.csproj
5. Adding a new library
- Create
dotcore/DotCore.<Name>/withDotCore.<Name>.csproj. - Obey dependency rule: only reference DotCore.* projects that are allowed (see §3).
- Add the project to
dotcore/dotcore.sln. - Update DOT_ARCHITECTURE.md and dotcore/DESIGN.md project list.
6. Adding a new app
- Create
dotapps/<AppName>/with<AppName>.csprojand entry point (e.g.Program.cs). - Set
RootNamespacetoDotApps.<AppName>,AssemblyNameto<AppName>. - Add ProjectReference only to required
dotcorelibs (path..\..\dotcore\DotCore.<Name>\DotCore.<Name>.csproj). - Add the project to
dotcore/dotcore.sln. - Optionally use
dotapps/start.ps1menu "Create new app" to scaffold.
7. Build and run
- From repo root:
dotnet build dotcore/dotcore.sln - Run app:
dotnet run --project dotapps/<AppName>/<AppName>.csproj(with optional args after--). - Menu:
.\dotapps\start.ps1(from repo root or fromdotapps/) for "Create new app" or "Run existing app".
8. Updating this skill / rules
- Canonical project spec: development-guides/DOT_ARCHITECTURE.md.
- Rule file: .cursor/rules/dot.mdc. Keep skill and rule in sync; avoid duplicate wording; reference by section (e.g. §3) where possible.
- UI rule: For WPF/MAUI/Blazor/Avalonia apps, also follow development-guides/DOT_UI_PROJECT_SPECIFICATION.md and .cursor/rules/dot-ui.mdc.
- When adding a new library or app, update DOT_ARCHITECTURE.md and DESIGN.md; optionally extend this SKILL.md Instructions.
Summary
| Need | Where | |------|--------| | Shared types / utilities used by more than one app | dotcore/DotCore.* | | Sub-app characteristic library (single-app domain types) | dotapps/<AppName>/<SubLib>/ (e.g. dotapps/d3check/D3CheckCore/) | | Runnable app | dotapps/<AppName>/ | | Canonical layout and naming | DOT_ARCHITECTURE.md | | Cursor rule (globs dotcore/, dotapps/) | .cursor/rules/dot.mdc | | UI layer (Clean Architecture + MVVM + Fluent 2) | DOT_UI_PROJECT_SPECIFICATION.md, .cursor/rules/dot-ui.mdc | | Build | dotnet build dotcore/dotcore.sln | | Run app | dotnet run --project dotapps/... or start.ps1 |
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/dot-stack-architecture-net-mm5t8c4g/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/dot-stack-architecture-net-mm5t8c4g' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/dot-stack-architecture-net-mm5t8c4g/download' --output '.skill-downloads/dot-stack-architecture-net-mm5t8c4g/SKILL.md.part' && mv '.skill-downloads/dot-stack-architecture-net-mm5t8c4g/SKILL.md.part' '.skill-downloads/dot-stack-architecture-net-mm5t8c4g/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/dot-stack-architecture-net-mm5t8c4g/SKILL.md' && test -s '.skill-downloads/dot-stack-architecture-net-mm5t8c4g/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/dot' && cp -R '.skill-downloads/dot-stack-architecture-net-mm5t8c4g' '.claude/skills/dot'Cursor
test -f '.skill-downloads/dot-stack-architecture-net-mm5t8c4g/SKILL.md' && test -s '.skill-downloads/dot-stack-architecture-net-mm5t8c4g/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/dot' && cp -R '.skill-downloads/dot-stack-architecture-net-mm5t8c4g' '.cursor/skills/dot'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/dot-stack-architecture-net-mm5t8c4g'openskills read 'dot-stack-architecture-net-mm5t8c4g'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/dot-stack-architecture-net-mm5t8c4g/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.