Start an alternative to Clip Studio Paint.

Pick one workflow.

“Replace the whole product” is too broad for a first milestone. Pick an input, a user action and an output: import a file, adjust one property, then save a result. Write down who needs it and the gap existing tools leave.

Check the alternatives already listed for this product. A contribution to an existing tool may cover your need; a new project should explain the different workflow or approach it offers.

Study behavior before implementation.

Record the product version, environment, input fixtures, actions and outputs. Capture normal cases and failures. Start with public documentation and file-format specifications, then inspect software you own or are authorized to examine.

Keep observations separate from guesses. Write a behavior specification with examples that another person can reproduce. Use your own or redistributable fixtures, code and assets; retain the licenses of dependencies and any permitted reused material.

Set up REA with your coding agent.

REA connects an agent to analysis tools for binaries, applications and runtime behavior. It provides evidence for an investigation; the agent writes and tests your implementation.

The documented runtime is Node.js 22.19+ in the 22.x line, 24.11+ in the 24.x line, or 26+, with npm. Run setup, select the agent you use, review its configuration changes and approve the plan. Restart that agent after setup.

npx rea-agents@latest setup

Native analysis uses a configured Hopper, Ghidra or IDA provider. Static JavaScript/Electron inspection needs no native analysis engine. Linux workflows also need a procps-compatible ps. Follow the provider’s installation and host requirements.

npx -y rea-agents@latest doctor --json

Investigate the feature with evidence.

Give your agent the target and a narrow question. REA’s guided investigation distinguishes observed facts, inferred behavior and unresolved questions. Inspect relevant strings, modules, routes, references or routines, then connect findings to your test cases.

Use REA to investigate Clip Studio Paint, focusing on one small workflow, such as opening a document, changing it and exporting the result. I will supply an authorized local target or test environment. Identify its version and the available analysis tools. Trace only the parts relevant to this workflow. Cite the evidence for each finding and separate observations, inferences and unknowns. Produce a behavior specification and test cases. Ask before running the target or changing its state.

npx -y rea-agents@latest analyze-javascript-application /absolute/path/to/app --json

npx -y rea-agents@latest analyze /absolute/path/to/program --provider ghidra --json

Static inspection does not establish every runtime behavior. If a finding needs an experiment, use a disposable target and explicit actions, then record what happened. Analysis takes place locally, but tool results sent to your coding agent are subject to that model provider’s data policy.

Build and verify an original implementation.

Choose a stack you can maintain. Implement the smallest complete workflow first, including useful errors and a documented way to run it. Track unsupported behavior instead of filling gaps with guessed compatibility claims.

Build an original open implementation of one small workflow, such as opening a document, changing it and exporting the result. Work from the behavior specification and public format documentation. Propose the smallest useful milestone, then implement it in my repository. Test the observable inputs and outputs, error cases, save/reopen behavior and compatibility using fixtures I can redistribute. List what works, what is missing and what remains unverified.

• Check import/export and save/reopen behavior with reproducible fixtures.
• Test undo, empty inputs, malformed files and cancellation where relevant.
• Check keyboard use, readable contrast and assistive-technology labels.
• Compare outputs and explain tolerances; a similar screenshot alone does not prove compatibility.
• Document how data stays portable and how someone can leave your tool.

Start the project in public.

After listing your repository, follow its claim panel to prove repository write access. Once verified, it becomes an owned Commons project with a team and progress updates.

Create a repository with an explicit license, a README, setup instructions, an issue tracker and a small roadmap. Name the first milestone and write one contribution issue with a clear acceptance check. Invite testing, documentation, design, translation and accessibility work alongside code.

The editable workflow above is included in this starter brief. Fill in its unknowns, create your repository, then share the project here with an honest status and the products it helps replace.

# Open alternative project brief

Product: Clip Studio Paint
Workflow: one small workflow, such as opening a document, changing it and exporting the result

## First milestone
- One complete input → action → output path
- Known gaps and explicit non-goals

## Evidence
- Target version and environment
- Public docs and permitted observations
- Observations / inferences / unknowns

## Implementation
- Original code and assets; record dependency licenses
- Public repository, license and build instructions

## Verification
- Reproducible fixtures and expected outputs
- Error handling, save/reopen and import/export checks

## Help wanted
- One small issue with an acceptance check
- Documentation, accessibility, translations and testing

## Commons
- Link this project to Clip Studio Paint
- Describe readiness and gaps honestly