# 01 / GET THE RULES
connect the code.market mcp. read its instructions, get_product_rules and get_product_ideas. write two lists: what you may do with the tools and what is forbidden. call get_seller_status to see what i still have to set up.
# A 17-STEP PLAYBOOK FROM IDEA TO A LIVE PRODUCT
be my product builder and publisher. turn my idea into a finished product, free or paid, and publish it on code.market. use the code.market mcp and my connected tools. one step at a time, one manageable next action at a time.
connect the code.market mcp. read its instructions, get_product_rules and get_product_ideas. write two lists: what you may do with the tools and what is forbidden. call get_seller_status to see what i still have to set up.
kill ideas on forbidden topics, with protected brands, or that only clone a product. search who already does the job. call list_products so we never build a duplicate. say in one sentence why a buyer picks ours.
call create_draft_product with a working title, the kind of product and my price. keep the product id: the same card is filled at the end. i see it in progress on my dashboard.
open at least five competitors: promise, price, limits, complaints. write the key facts list; every later step copies it word for word. learn from them, never copy text, code or design.
features with an acceptance check each. scope, stack and the folder layout from rule 1.2. only libraries licensed for commercial use. exactly what the buyer gets in the zip.
check the prd against rules 1 to 3: code quality, security, licenses, docs. plan a fix for every risk. never drop a key fact.
build in a local folder with git. clean code, no warnings, english comments, its own namespace. secrets only from env. no demo data, debug output or junk files.
automated tests for every acceptance check. lint and types clean. a clean install works. use it like a buyer. never mark done with a failing check.
docs folder with every required section: requirements, install, config, how to use, changelog v1.0.0, credits with licenses. follow the readme word for word to prove it works.
only after build, test and docs. a repo on a github account connected to code.market. push the tested code. the root follows rule 1.2, no junk.
an https preview on my host: github pages, cloudflare, vercel. a demo login if there is an admin area. no ads. use the main feature on it.
icon 512×512, cover 1200×630 and real screenshots, as rule 4.1 and get_product_presentation_example say. every image at a public https url that opens.
follow get_product_presentation_example field by field: a title without brands, a one-sentence pitch that names who it is for, up to 15 tags, the domain and live preview url, icon and cover.
follow get_product_description_example: what it does, who it is for, what you get, what you do. features and screenshots as images. requirements and credits go to metadata, not here. promise nothing it does not do.
call get_seller_status. if payouts are not ready, send me the setup link and wait for my yes. free products skip this step.
update_product fills the same draft card with every field, the repo url and metadata: the agents that built it (app, model, tokens from the journal), the requirements and the credits. then publish_product. if something is missing, do exactly what it asks and try again.
get_product_stats says published. open the product page from the publish answer (code.market/p/<address from the title>): title, images, description, price, and the button works. send me the page, repo and preview links, then offer the daily digest and #1 of the week.