New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Directory Build Organization

by rodri-oliveira-dev in rodri-oliveira-dev/Dapper-FluentMap

Guide for organizing MSBuild infrastructure with Directory.Build.props, Directory.Build.targets, Directory.Packages.props when present, and related repository build files.

MITAuto-check passedDevelopment

Install Directory Build Organization

skills CLI
$ npx skills add rodri-oliveira-dev/Dapper-FluentMap --skill directory-build-organization -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install rodri-oliveira-dev/Dapper-FluentMap directory-build-organization --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/rodri-oliveira-dev/Dapper-FluentMap.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/directory-build-organization .claude/skills/directory-build-organization && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
directory-build-organization
GitHub stars
454
Token cost
~1k tokens
SKILL.md length
344 words
Files
4 (incl. references)
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Guide for organizing MSBuild infrastructure with Directory.Build.props, Directory.Build.targets, Directory.Packages.props when present, and related repository build files.

  • Works in 7 steps: Audit relevant .csproj, root… → Identify duplicated vs project-specific… → Preserve ownership of package identity,… → …
  • : structuring multi-project repos
  • SKILL.md covers Evaluation order, Dependency-version organization, Multi-level Directory.Build… and Workflow, plus 1 more section
  • Calls dotnet

What it does

Directory Build Organization is an agent skill from rodri-oliveira-dev/Dapper-FluentMap. Guide for organizing MSBuild infrastructure with Directory.Build.props, Directory.Build.targets, Directory.Packages.props when present, and related repository build files. USE FOR: structuring multi-project repos, consolidating duplicated properties, understanding MSBuild evaluation order, or evaluating whether Central Package Management would be appropriate. Critical pitfall: TargetFramework-dependent properties in .props may evaluate too early.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/common-patterns.md`, `references/multi-level-examples.md` and `references/targetframework-props-pitfall.md`).

It sits in Development. The repository describes itself as: Fluent mapping for Dapper, with conventions, immutable object materialization, analyzers, source generators, DI integration, and Dommel support. The licence is MIT.

When your agent uses it

  • : structuring multi-project repos
  • Consolidating duplicated properties
  • Understanding MSBuild evaluation order
  • Evaluating whether Central Package Management would be appropriate

Example prompts

  • “/directory-build-organization”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Audit relevant .csproj, root Directory.Build.props, Directory.Build.targets, and any subtree build files.
  2. Identify duplicated vs project-specific settings.
  3. Preserve ownership of package identity, versioning, compatibility, analyzers, warnings, pack metadata and consumer-smoke behavior.
  4. Move only clearly shared defaults into .props.
  5. Keep custom targets/late SDK-dependent logic in .targets.
  6. Validate SLNX equivalence if project structure changes.
  7. Validate restore/build/test and pack/consumer-smoke when packaging semantics could be affected.

What it can do on your machine

Read from SKILL.md and the folder at commit 4f5a39f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • dotnet

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Directory Build Organization loads about 1k tokens when it runs, and up to ~2.1k if it reads all its reference files. Until then it costs about 120 tokens; SKILL.md has 344 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~120
When it runs · the whole SKILL.md, loaded when a task matches
~1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from rodri-oliveira-dev/Dapper-FluentMap at commit 4f5a39f, republished under its MIT licence (© rodri-oliveira-dev). 344 words, ~1,002 tokens.

Download SKILL.mdSave it as .claude/skills/directory-build-organization/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
directory-build-organization
description
Guide for organizing MSBuild infrastructure with Directory.Build.props, Directory.Build.targets, Directory.Packages.props when present, and related repository build files. USE FOR: structuring multi-project repos, consolidating duplicated properties, understanding MSBuild evaluation order, or evaluating whether Central Package Management would be appropriate. Critical pitfall: TargetFramework-dependent properties in .props may evaluate too early.
license
MIT

Organizing Build Infrastructure with Directory.Build Files

Dapper-FluentMap integration: this repository already uses root Directory.Build.props and Directory.Build.targets, plus a separate eng/consumer-smoke/Directory.Build.props. It does not currently use Directory.Packages.props/Central Package Management. Preserve that actual structure unless CPM migration is explicitly requested and justified. Package identity also lives in eng/package-catalog.json; do not move PackageIds casually into generic build defaults.

Evaluation order

text
Directory.Build.props → SDK .props → .csproj → SDK .targets → Directory.Build.targets
Use .props forUse .targets for
property defaultscustom build targets
common itemslate-bound property overrides
shared package/assembly metadatalogic depending on final SDK properties
shared dependency-version propertiespost-build/pack validation
TargetFramework pitfall

Property conditions on $(TargetFramework) in .props files can silently fail for single-target projects because the project may set the TFM after .props import. Move such property logic to .targets or the project file. See references/targetframework-props-pitfall.md.

Dependency-version organization

The repository currently uses a mixed explicit model:

  • shared ranges/properties such as Dapper/Dommel versions live in Directory.Build.props;
  • many package versions remain explicit in individual .csproj files;
  • consumer-smoke package versioning is isolated under eng/consumer-smoke/Directory.Build.props.

Do not describe this repository as using CPM unless a Directory.Packages.props with ManagePackageVersionsCentrally actually exists. A future CPM migration is a dedicated dependency-governance change, not incidental cleanup.

Multi-level Directory.Build files

MSBuild auto-imports the first Directory.Build.props/.targets it finds walking upward. If a subtree intentionally uses another file, verify whether it needs to import the parent or intentionally isolates itself. See references/multi-level-examples.md.

Workflow

  1. Audit relevant .csproj, root Directory.Build.props, Directory.Build.targets, and any subtree build files.
  2. Identify duplicated vs project-specific settings.
  3. Preserve ownership of package identity, versioning, compatibility, analyzers, warnings, pack metadata and consumer-smoke behavior.
  4. Move only clearly shared defaults into .props.
  5. Keep custom targets/late SDK-dependent logic in .targets.
  6. Validate SLNX equivalence if project structure changes.
  7. Validate restore/build/test and pack/consumer-smoke when packaging semantics could be affected.

Useful diagnosis:

bash
dotnet msbuild -pp:output.xml path/to/Project.csproj

Validation

  • No TargetFramework-dependent property was moved to an early .props evaluation point
  • Existing explicit dependency-version model remains consistent unless migration was in scope
  • Project-specific settings were not generalized without evidence
  • eng/package-catalog.json remains authoritative for package identities
  • Restore/build/test still pass
  • Packaging metadata/output remains unchanged unless intentionally modified

See references/common-patterns.md for common layouts and validation examples.

© rodri-oliveira-dev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in .agents/skills/directory-build-organization of rodri-oliveira-dev/Dapper-FluentMap.

  • SKILL.md
  • references/common-patterns.md
  • references/multi-level-examples.md
  • references/targetframework-props-pitfall.md

Open the folder on GitHubat commit 4f5a39f

Compare with similar skills

Directory Build Organization next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Directory Build Organization compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Directory Build Organization this skillrodri-oliveira-dev/Dapper-FluentMap454—~1kAutomated safety check: PassMIT
Vercel Composition Patternssupabase/supabase111k58 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k4 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Vercel Composition Patterns

    supabase/supabase

    Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 58 repos~726 tokens
    DevelopmentAuto-check passed

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 4 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

More from rodri-oliveira-dev/Dapper-FluentMap

All 11 skills in this repo

  • Microbenchmarking

    rodri-oliveira-dev/Dapper-FluentMap

    Activate when BenchmarkDotNet is involved or when a .NET performance question requires controlled microbenchmark measurement.

    454 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Nuget Trusted Publishing

    rodri-oliveira-dev/Dapper-FluentMap

    Review, maintain, or set up NuGet trusted publishing (OIDC) for GitHub Actions.

    454 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed

  • Test Gap Analysis

    rodri-oliveira-dev/Dapper-FluentMap

    Pseudo-mutation analysis for behavioral blind spots: determine whether existing tests would catch meaningful caller-visible production changes, identify survivors or untested outcomes, and…

    454 GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed

  • Authoring GitHub Workflows

    rodri-oliveira-dev/Dapper-FluentMap

    Author and review GitHub Actions workflow YAML safely so syntactically-valid YAML can't ship a workflow that GitHub Actions refuses to run.

    454 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Binlog Failure Analysis

    rodri-oliveira-dev/Dapper-FluentMap

    Analyze MSBuild binary logs to diagnose build failures. An agent skill from rodri-oliveira-dev/Dapper-FluentMap.

    454 GitHub stars~750 tokensUpdated yesterday
    Auto-check passed

  • CI Release Governance

    rodri-oliveira-dev/Dapper-FluentMap

    A skill your agent uses to review or adjust Dapper-FluentMap GitHub Actions, packaging, NuGet publishing, versioning, release, rollback, recovery, provenance, and automation security.

    454 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Directory Build Organization

What does Directory Build Organization do?

Guide for organizing MSBuild infrastructure with Directory.Build.props, Directory.Build.targets, Directory.Packages.props when present, and related repository build files. Directory Build Organization is an agent skill from rodri-oliveira-dev/Dapper-FluentMap.props when present, and related repository build files.

When should I use Directory Build Organization?

Directory Build Organization fits situations like: : structuring multi-project repos; consolidating duplicated properties; understanding MSBuild evaluation order; evaluating whether Central Package Management would be appropriate.

How do I install Directory Build Organization in Claude Code?

Run `npx skills add rodri-oliveira-dev/Dapper-FluentMap --skill directory-build-organization -a claude-code`. Or copy the skill folder (.agents/skills/directory-build-organization in rodri-oliveira-dev/Dapper-FluentMap) into .claude/skills/directory-build-organization in your project. Claude Code loads it when a task matches its description.

How do I install Directory Build Organization in Codex?

Run `npx skills add rodri-oliveira-dev/Dapper-FluentMap --skill directory-build-organization -a codex`. Or copy the skill folder (.agents/skills/directory-build-organization in rodri-oliveira-dev/Dapper-FluentMap) into .agents/skills/directory-build-organization in your project. Codex loads it when a task matches its description.

Can I use Directory Build Organization in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rodri-oliveira-dev/Dapper-FluentMap --skill directory-build-organization -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/directory-build-organization, .gemini/skills/directory-build-organization, .github/skills/directory-build-organization and .opencode/skills/directory-build-organization in your project.

What does Directory Build Organization need to run?

Going by SKILL.md and its folder, Directory Build Organization needs the command-line tools its instructions call (dotnet).

Does Directory Build Organization access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Directory Build Organization safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Directory Build Organization use?

Directory Build Organization is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Directory Build Organization use?

About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.

What are the alternatives to Directory Build Organization?

Skills that share tags, products or a category with Directory Build Organization: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Directory Build Organization?

rodri-oliveira-dev (a GitHub user) maintains it in rodri-oliveira-dev/Dapper-FluentMap, which has 454 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 8, 2026.

Source: rodri-oliveira-dev/Dapper-FluentMap on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.