Enter with context
Join an existing teaching product with history, conventions, and imperfect code—not a blank tutorial repo.
Guided engineering practice // active build
Practice the job before you have the job.
SpellStack is a mentor-built practice environment where early-career developers join an evolving product, work through scoped changes, and grow through realistic review loops.
The work is the curriculum.Noncommercial. Mentor-guided. Evidence-backed.
storeforge / pull-request
STACK-42
MergedDelete an inventory card
Trace the existing API flow, implement the endpoint, add a Bruno request, and revise the change through review.
Ticket→Branch→Review→QA
CardsController.csauthored by John
await cardService.DeleteCardByIdAsync(id);01Existing codebase
02Real team workflow
03Built for learning
The missing middle
Knowing code is not the same as knowing the work.
Tutorials can teach syntax, frameworks, and patterns. A first developer role also asks someone to navigate ambiguity, read code they did not write, communicate tradeoffs, and improve a product that keeps changing.
SpellStack creates a guided place to build those muscles before the stakes are a paycheck and a production system.
How the system works
The ordinary loop where engineering judgment grows.
Small, product-shaped assignments are selected for educational value. They repeat the habits of a healthy software team without making the learner responsible for operating a business.
Work a scoped ticket
Clarify the problem, find the relevant code, and make the smallest useful change on a focused branch.
Ship through review
Open a pull request, explain the approach, respond to feedback, and hand the work to QA.
Turn work into judgment
Reflect on tradeoffs, debugging, and feedback so each ticket builds transferable engineering instincts.
The environment is part of the work
Realistic practice has to be carefully built.
SpellStack is not a company looking for free output. The mentor creates and maintains the product environment, learning path, scaffolding, review, and support that make the practice useful.
A product with context
The mentor maintains StoreForge, its architecture, documentation, product history, and deliberately imperfect edges.
Learning-shaped work
Tickets are scoped around the developer's next useful stretch—not around a client deadline or production quota.
A thoughtful feedback loop
Review, QA scenarios, pairing, and reflection turn completed code into better engineering judgment.
The TCG product environment
A specific domain makes the practice real.
StoreForge models the operational complexity of a trading card game store. Cards cross games, sets, printings, conditions, languages, and variants; stores also manage organized play, customer relationships, and store credit.
That connected domain gives each exercise meaningful constraints while keeping the product independent from any one game or publisher.
See work from the codebaseSTOREFORGE.SYS● active
01 / interfaceReact + TypeScript
02 / applicationASP.NET Core API
03 / persistenceMongoDB
Multi-game catalogSets & printingsCondition & variantsOrganized playStore creditCustomer relationships
Learning in practice // current participant
Authentic practice. Clear ownership.
John is the first developer participating in SpellStack's guided practice environment. His work is selected for learning value and moves through tickets, branches, pull requests, review, and QA—not client delivery or production obligation.
Inventory foundations
Model and DTO validation, MongoDB-backed persistence, and create-flow improvements.
Repository evidence forthcomingCard detail API
A focused endpoint for retrieving a single inventory card through the established service layers.
Repository evidence forthcomingInventory deletion
Controller, service, repository, and Bruno coverage revised through pull-request feedback.
Repository evidence forthcomingThe goal is not to make someone look experienced. It is to help them become experienced.
Built for learning, not labor
A teaching product—not an unpaid job.
StoreForge has no paying customers, and SpellStack does not depend on participant output to operate. The product exists to provide a persistent codebase with realistic constraints, history, and room to learn from mistakes.
The mentor invests the time to create and maintain the environment, scope appropriate work, review contributions, and teach. Participants learn at an appropriate pace and can carry evidence of their work into future opportunities.
- Noncommercial mentorship project
- No customer or production dependency
- No promise or guarantee of employment