Install the "development-workflow" agent skill from https://github.com/runceel/ReactiveProperty/tree/main/.agents/skills/development-workflow into .claude/skills/development-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "development-workflow", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add runceel/ReactiveProperty --skill development-workflow -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "development-workflow" agent skill from https://github.com/runceel/ReactiveProperty/tree/main/.agents/skills/development-workflow into .agents/skills/development-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "development-workflow", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add runceel/ReactiveProperty --skill development-workflow -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "development-workflow" agent skill from https://github.com/runceel/ReactiveProperty/tree/main/.agents/skills/development-workflow into .cursor/skills/development-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "development-workflow", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add runceel/ReactiveProperty --skill development-workflow -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "development-workflow" agent skill from https://github.com/runceel/ReactiveProperty/tree/main/.agents/skills/development-workflow into .gemini/skills/development-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "development-workflow", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add runceel/ReactiveProperty --skill development-workflow -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "development-workflow" agent skill from https://github.com/runceel/ReactiveProperty/tree/main/.agents/skills/development-workflow into .github/skills/development-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "development-workflow", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add runceel/ReactiveProperty --skill development-workflow -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "development-workflow" agent skill from https://github.com/runceel/ReactiveProperty/tree/main/.agents/skills/development-workflow into .opencode/skills/development-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "development-workflow", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
development-workflow
GitHub stars
944
Token cost
~1.4k tokens
SKILL.md length
586 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
MIT
At a glance
ReactiveProperty repository development policy. An agent skill from runceel/ReactiveProperty.
Works in 3 steps: TDD is mandatory — Red → Green → Refactor → Record design decisions as ADRs → Documentation split: docs/ vs dev-docs/
You implement a feature
SKILL.md covers When to Use, When Not to Use, 1. TDD is mandatory — Red →… and 2. Record design decisions as…, plus 2 more sections
Calls dotnet
What it does
Development Workflow is an agent skill from runceel/ReactiveProperty. ReactiveProperty repository development policy. Use whenever you implement a feature or bug fix, change library or test code under Source/ or Test/, make a design or architecture decision, or write documentation in this repo. Enforces strict Test-Driven Development (Red - Green - Refactor) with MSTest and dotnet test ReactiveProperty.slnx, requires recording design decisions as ADRs under dev-docs/adr/, and defines the documentation split: docs/ is user-facing (plain Markdown browsed on GitHub) while dev-docs/…
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Architecture decision records, Test-driven development and Debugging. It works with .NET and GitHub. The repository describes itself as: ReactiveProperty provides MVVM and asynchronous support features under Reactive Extensions. Target frameworks are .NET 6+, .NET Framework 4.7.2 and .NET Standard 2.0. The licence is MIT.
When your agent uses it
You implement a feature
Test code under Source/
Architecture decision
Write documentation in this repo
Example prompts
“implement”
“add feature”
“fix bug”
“/development-workflow”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit e7e6474. 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
Development Workflow loads about 1.4k tokens when it runs. Until then it costs about 189 tokens; SKILL.md has 586 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~189
When it runs· the whole SKILL.md, loaded when a task matches
~1.4k
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.
Download SKILL.mdSave it as .claude/skills/development-workflow/SKILL.md (or your agent's skills folder).
name
development-workflow
description
ReactiveProperty repository development policy. Use whenever you implement a feature or bug fix, change library or test code under Source/ or Test/, make a design or architecture decision, or write documentation in this repo. Enforces strict Test-Driven Development (Red -> Green -> Refactor) with MSTest and `dotnet test ReactiveProperty.slnx`, requires recording design decisions as ADRs under dev-docs/adr/, and defines the documentation split: docs/ is user-facing (plain Markdown browsed on GitHub) while dev-docs/ holds implementer/contributor documentation. Triggers include "implement", "add feature", "fix bug", "TDD", "red green refactor", "design decision", "architecture", "ADR", "where do docs go", and "contributor docs".
Development Workflow (ReactiveProperty)
The required development workflow and documentation policy for this repository.
When to Use
Implementing any feature or bug fix in Source/ or Test/.
Making a design or architecture decision (public API shape, threading model, new package, dependency, breaking change).
Deciding where a piece of documentation belongs.
When Not to Use
Pure release/versioning mechanics (see AGENTS.md and the build/publish workflow).
One-off exploration or read-only investigation with no code change.
1. TDD is mandatory — Red → Green → Refactor
Every code change to Source/ must be driven by a failing test first. Follow the cycle
strictly and do not skip steps:
Red — Write the smallest test that expresses the desired behavior, then run it and
watch it fail. The failure must be for the right reason (asserting the new behavior,
not a compile error you didn't expect).pwsh
dotnet test ReactiveProperty.slnx
Narrow the loop while iterating, e.g. a single project or filter:pwsh
dotnet test Test/ReactiveProperty.NETStandard.Tests/ReactiveProperty.NETStandard.Tests.csproj --filter "FullyQualifiedName~YourNewTest"
Green — Write the minimum production code to make the test pass. Re-run the
tests and confirm they are green. Don't add unrequested functionality.
Refactor — With tests green, clean up production and test code (naming, duplication,
structure). Re-run tests after refactoring; they must stay green. Behavior must not change.
Rules:
Never write production code without a failing test that requires it.
Keep each Red→Green→Refactor cycle small and focused on one behavior.
A change is not "done" until dotnet test ReactiveProperty.slnx passes on Windows
(WPF/UWP projects require Windows).
Helpers available: Moq, Microsoft.Reactive.Testing (TestScheduler for time-based
Rx), the bundled ChainingAssertion (actual.Is(expected) fluent assertions); Blazor
tests use bunit.
Put tests in the matching Test/* project; the core test project uses namespace
ReactiveProperty.Tests.
Keep new Source/ code compatible with netstandard2.0 / net472 (lowest TFMs).
See the writing-mstest-tests and run-tests skills for MSTest authoring details and
filter/runner syntax.
Show full SKILL.md (287 more words)Show less
2. Record design decisions as ADRs
Going forward, every non-trivial design / architecture decision is recorded as an
Architecture Decision Record (ADR).
Write an ADR when you:
add or remove a public API surface, or change its semantics;
add a new package/project or a new external dependency;
change threading/scheduling, validation, or serialization behavior;
make a breaking change or deprecate something;
choose between competing implementation approaches with long-term impact.
How:
ADRs live in dev-docs/adr/, one file per decision.
Copy dev-docs/adr/template.md, name it NNNN-short-title.md with the next zero-padded
number (e.g. 0002-...), and fill in Status, Context, Decision, Consequences.
New ADRs start as Status: Proposed; mark Accepted once agreed. Don't edit accepted
ADRs to reverse a decision — add a new ADR that supersedes the old one and update both
Status lines.
Add the new ADR to the index in dev-docs/adr/README.md.
Trivial, reversible choices (local refactors, naming) do not need an ADR.
3. Documentation split: docs/ vs dev-docs/
docs/ = user-facing documentation, plain Markdown browsed directly on GitHub (no site
generator). Write here for library consumers: getting-started, API usage,
samples. Available in English and Japanese (*-ja). Keep links relative (.md).
dev-docs/ = implementer/contributor-facing documentation, not published.
Write here for people working on ReactiveProperty: architecture notes, internal design,
contributor workflow, and ADRs (dev-docs/adr/).
When you add documentation, pick the audience first:
"How does a consumer use this feature?" → docs/.
"How/why is this implemented, or how do I contribute?" → dev-docs/.
Checklist before finishing a change
Behavior was driven by a failing test first (Red), then made to pass (Green), then refactored.
dotnet test ReactiveProperty.slnx passes.
New Source/ code stays compatible with netstandard2.0 / net472.
Any design/architecture decision is captured as an ADR in dev-docs/adr/ and indexed.
New docs placed by audience (docs/ for users, dev-docs/ for implementers).
Development Workflow 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.
Development Workflow compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Development Workflow this skillrunceel/ReactiveProperty
A skill your agent uses when the user or project explicitly adopts hexagonal (ports and adapters) architecture — a README, CLAUDE.md, or ADR that says so is the opt-in.
ReactiveProperty repository development policy. An agent skill from runceel/ReactiveProperty. Development Workflow is an agent skill from runceel/ReactiveProperty. ReactiveProperty repository development policy.
When should I use Development Workflow?
Development Workflow fits situations like: you implement a feature; test code under Source/; architecture decision; write documentation in this repo.
How do I install Development Workflow in Claude Code?
Run `npx skills add runceel/ReactiveProperty --skill development-workflow -a claude-code`. Or copy the skill folder (.agents/skills/development-workflow in runceel/ReactiveProperty) into .claude/skills/development-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Development Workflow in Codex?
Run `npx skills add runceel/ReactiveProperty --skill development-workflow -a codex`. Or copy the skill folder (.agents/skills/development-workflow in runceel/ReactiveProperty) into .agents/skills/development-workflow in your project. Codex loads it when a task matches its description.
Can I use Development Workflow 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 runceel/ReactiveProperty --skill development-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/development-workflow, .gemini/skills/development-workflow, .github/skills/development-workflow and .opencode/skills/development-workflow in your project.
What does Development Workflow need to run?
Going by SKILL.md and its folder, Development Workflow needs the command-line tools its instructions call (dotnet).
Does Development Workflow 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 Development Workflow 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 Development Workflow use?
Development Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Development Workflow use?
About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Development Workflow?
Skills that share tags, products or a category with Development Workflow: Triage Issue (softspark/ai-toolkit, 179 stars), MAUI Regression Tracer (dotnet/maui, 23k stars), Hexagonal Architecture (citypaul/.dotfiles, 739 stars) and Project Context Setup (Mathews-Tom/armory, 327 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Development Workflow?
runceel (a GitHub user) maintains it in runceel/ReactiveProperty, which has 944 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on August 31, 2026.
Source: runceel/ReactiveProperty on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
