I will set up your project context file and rules for any coding tool


About this gig
Tired of your coding assistant ignoring your code style, folder layout and your "never commit to main" rule?
I write the project context file and rules for any coding tool - Cursor, Codex, or anything else that reads a project context file.
WHAT YOU GET
- A tailored project context file (AGENTS.md / CLAUDE.md / .cursorrules - your choice) with your stack, build / test / lint commands, code conventions and a yes / no rules list
- The matching config folder for your tool (.claude/, .cursor/, .minimax/ etc.) in that tool's native format
- Custom commands for your repeat tasks, written in the native format of YOUR tool
- A permission allowlist for routine commands, plus a deny-list blocking .env, secrets, git push and rm -rf
- A README handoff so you can maintain it without me
WHY ME
I ship developer tooling for a living: a Chrome extension on a Cloudflare Worker licence API, a serverless backend, and my own project-context packs.
My day job is geospatial and survey data pipelines, so I treat rules like production config: versioned, documented, reproducible.
Any stack: Node/React, Python, Go, Rust, PHP and more. Message me with your tool, stack and goals.
Get to know Jiaming
GIS Survey Data Engineer and Python, ArcGIS, Land Parcel and Field Data
- FromChina
- Member sinceJul 2026
Languages
Chinese, English
My Portfolio
Other Software Development Services I Offer
FAQ
Can you set it up for my specific tool?
Yes - tell me the tool and version and I deliver that tool's native format, not a renamed copy of another tool's config. For the full feature set (hooks, subagents, MCP wiring), message me and I will scope that as a separate job.
What if my team uses more than one tool?
That is fine. One shared context file covers the rules and I add the small per-tool config each one needs. Just tell me the list.
Will this really stop it ignoring my rules?
Mostly. The context file is read automatically by tools that support it, and the commands give a repeatable entry point for your daily tasks. Not magic, but it removes the most common complaint.
Do I need to give you repo access?
Not necessarily - I can work from a description of your stack and conventions. Read-only access helps for a deeper setup, but it is your call.
How fast will you reply and start?
I reply within 3-4 hours, usually the same working day. You get my recommended approach and a clear price before any work starts. If your task needs more time or a different approach, I will say so straight away instead of going quiet.

