QIMING / CASES

Real cases

See each starting point, what changed, what remains, and what has not been verified.

Computer careQiming adopted

A development computer rebuilt again and again

The problem

I often reinstall my operating system. Software, scripts, and account information were scattered across conversations and folders, so every restart needed another explanation.

What happened

I gave the computer its own management directory. Qiming checked the current system and existing records, registered a long-lived media tool as a member, and tracked installation separately from functional verification.

What remains

A short entry now points to the system check, tool record, installation result, and next task. Account records contain secure-storage references, not passwords.

Verified boundary

The service and management page were connected. Actual generation is still unverified, and backup recovery remains to be checked.

Ask your agent

$qiming Continue managing this computer. Check the current system and existing records, decide whether this new tool needs a member record, and separate installation, real function testing, and next steps.

Complex developmentQiming adopted in the main project

A health project with a contract and several roles

The problem

This health project combines contract scope, two active codebases, several roles, and a customer preview. An old development directory remains for history and can be mistaken for the live delivery location.

What happened

I adopted Qiming at the main project root. It preserved the existing rules and connected both codebases, delivery evidence, and the current task through a short entry. A project Skill and AGENTS.md give new sessions their starting point.

What remains

The main directory now has its own instance, work records, and asset ownership. Verified preview work is tracked separately from remaining contract requirements. The old directory is an archive and is not used for releases.

Verified boundary

The main instance and Codex binding passed checks. The old directory has no separate Qiming instance. A customer preview is not final contract acceptance, and sessions started inside either codebase still need a scope check.

Ask your agent

$qiming Continue from the main project root. Read its entry, existing rules, and current task; check both active codebases and delivery evidence. Do not develop from the archive, and track the preview separately from final acceptance.

Website operations and product careProject adopted

Qiming manages its own website

The problem

The website, Skill source, public package, and management records are maintained in one project.

What happened

A short entry connects site work, domain verification, release review, and user feedback. Local checks and public results are recorded separately.

What remains

The four languages, official domain, and public install were previously checked. This redesign needs a new build, release, and live verification.

Ask your agent

Continue maintaining Qiming's website. Read the current task and latest feedback, update the site and Skill, then verify the local build, public package, and official domain separately. Leave the next step.