dot — for Claude Code core_node, community, for Claude Code, ide skills, dotcore, dotapps, DotCore.Foundations, SimpleUi, CallModule, d3check

v1.0.0
GitHub

About this Skill

Ideal for AI agents that need dot stack skill (dotcore + dotapps). dot is an AI agent skill for dot stack skill (dotcore + dotapps).

Features

Dot Stack Skill (dotcore + dotapps)
Use this skill when editing or adding code under dotcore/ or dotapps/ .
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).

# Core Topics

for Claude Code dotcore dotapps DotCore.Foundations SimpleUi CallModule
accountbelongstox accountbelongstox
[0]
[0]
Updated: 4/4/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 8/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
8/11
Quality Score
48
Canonical Locale
zh
Detected Body Locale
zh

Ideal for AI agents that need dot stack skill (dotcore + dotapps). dot is an AI agent skill for dot stack skill (dotcore + dotapps).

Core Value

dot helps agents dot stack skill (dotcore + dotapps). Dot Stack Skill (dotcore + dotapps) Use this skill when editing or adding code under dotcore/ or dotapps/ . This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Ideal Agent Persona

Ideal for AI agents that need dot stack skill (dotcore + dotapps).

↓ Capabilities Granted for dot

Applying Dot Stack Skill (dotcore + dotapps)
Applying Use this skill when editing or adding code under dotcore/ or dotapps/
Applying Editing or adding code under dotcore/ (any DotCore. project or tests)

! Prerequisites & Limits

  • Language: All code, comments, and user-facing strings in English . ASCII only in source code.
  • DotCore.Foundations: No project refs; BCL/minimal NuGet only.
  • DotCore.Common: Foundations only.

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is dot?

Ideal for AI agents that need dot stack skill (dotcore + dotapps). dot is an AI agent skill for dot stack skill (dotcore + dotapps).

How do I install dot?

Run the command: npx killer-skills add accountbelongstox/core_node/dot. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for dot?

Key use cases include: Applying Dot Stack Skill (dotcore + dotapps), Applying Use this skill when editing or adding code under dotcore/ or dotapps/, Applying Editing or adding code under dotcore/ (any DotCore. project or tests).

Which IDEs are compatible with dot?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for dot?

Language: All code, comments, and user-facing strings in English . ASCII only in source code.. DotCore.Foundations: No project refs; BCL/minimal NuGet only.. DotCore.Common: Foundations only..

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add accountbelongstox/core_node/dot. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use dot immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

dot

# Dot Stack Skill (dotcore + dotapps) Use this skill when editing or adding code under dotcore/ or dotapps/ . This AI agent skill supports Claude Code

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

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). Namespace DotCore.*.
  • 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>/ with DotCore.<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>.csproj and entry point (e.g. Program.cs).
  • Set RootNamespace to DotApps.<AppName>, AssemblyName to <AppName>.
  • Add ProjectReference only to required dotcore libs (path ..\..\dotcore\DotCore.<Name>\DotCore.<Name>.csproj).
  • Add the project to dotcore/dotcore.sln.
  • Optionally use dotapps/start.ps1 menu "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 from dotapps/) for "Create new app" or "Run existing app".

8. Updating this skill / rules

Summary

NeedWhere
Shared types / utilities used by more than one appdotcore/DotCore.*
Sub-app characteristic library (single-app domain types)dotapps/<AppName>/<SubLib>/ (e.g. dotapps/d3check/D3CheckCore/)
Runnable appdotapps/<AppName>/
Canonical layout and namingDOT_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
Builddotnet build dotcore/dotcore.sln
Run appdotnet run --project dotapps/... or start.ps1

Related Skills

Looking for an alternative to dot or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer