How to use Claude to build a bakery invoicing app
A developer used Claude Code with Devpost's skill pack to build Cuenta for his wife's bakery. The guided planning caught date, pricing, and workflow problems before implementation proceeded in checked slices.
dev.to
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Using [skill pack] in Claude Code, interview me one question at a time about [business] and its [existing workflow]. Draft scope, screen-by-screen requirements, and a technical specification for approval in sequence. Check local dates, historical invoice prices, money representation, and separate planning from billing. Build in small checked slices and flag decisions I should review.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- earlgreyhot1701d
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- The author built Cuenta with shelf counts, delivery entry, branded invoices, and a payment ledger. Planning caught date, price-history, and workflow issues. The supplied excerpt does not confirm that the bakery adopted it for daily operations.
- Human involvement
- The author approved each planning document, and every implementation slice was checked before the next began.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Ran the Devpost Learn skill pack in Claude Code inside VS Code.
- Answered the agent's questions to develop scope and planning documents.
- Approved each planning document before the next document began.
The author built Cuenta for his wife's wholesale bakery after her missing notebook exposed how much business information existed without a backup. The app brings shelf counts, deliveries, branded invoices, and payment tracking into a phone-first interface for her four cafe accounts.
He ran Devpost's six-file skill pack in Claude Code inside VS Code. The agent interviewed him one question at a time, turning his answers into scope, a screen-by-screen product requirements document, and a technical specification. He approved each document before work moved to the next.
Planning caught several concrete problems. UTC server time could assign the wrong local invoice date and number. Linking invoices to current menu prices could change historical bills, so invoices retain their own prices and amounts use whole cents. The agent also identified a mismatch between a successful mock-data demonstration and actual business adoption. Shelf counts were separated from invoicing because they support baking plans rather than billing.
After approval, the skill pack divided implementation into eight small slices, each checked before the next began. Agent reports identified decisions the author should check. The excerpt describes app features, but does not establish that his wife adopted it for daily business use.
Who it's for: Developers building a small business app with invoicing and an identifiable end user.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: dev.to · earlgreyhot1701d
Frequently asked questions
How did the author approve the plan?
The skill pack interviewed him one question at a time and produced scope, a product requirements document, and a technical specification. He approved each document before the next started.
What billing problems did planning catch?
The plan caught UTC dates potentially producing the wrong invoice date and number, and linked prices potentially changing old invoices. Invoices retain their own prices, with amounts stored in whole cents.
Does the source establish real business adoption?
No. The excerpt distinguishes hackathon completion from the goal of his wife using the app for her business. It describes the app and build process but does not confirm daily adoption.
More details
Remaining steps
- Resolved invoice date, historical price, and shelf-count workflow issues during planning.
- Built the app in eight small slices, checking each before the next started.
About this account
Claude Code interviewed the author, drafted planning documents, and made implementation decisions that it flagged for checking.
Platform: dev.to. Attribution: https://dev.to/earlgreyhot1701d/an-app-built-for-one-why-a-devpost-skill-pack-made-me-spec-it-anyway-knh. Prompt: Suggested (written by Agents In Use, not the author's). Sourced by the Agents In Use pipeline.
Credit: earlgreyhot1701d on dev.to
Source published
Added to Agents In Use
Source checked
Tools and topics
Claude Code · VS Code · Devpost Learn skill pack · Vercel
Invoicing · Small business · App development · Planning
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.