Extend Your First Legal Tool
Review the working foundation and choose one safe, small next feature.
You will leave with a connected legal research prototype and a repeatable method for extending it.
What you built in Part 1
- A local app created from a blank project with help from a coding agent.
- An authenticated connection to Descrybe Legal Engine.
- A diagnostic view of the available legal research tools.
- A concept-search request with structured case results.
- A case-details request driven by a selected case ID.
- A practical loop for diagnosing launch and interface problems.
Run the full acceptance check
- 1Start the app from a clean stopped state.
- 2Open or refresh the local browser page.
- 3Connect the current user to Descrybe.
- 4List the available tools.
- 5Run a concept search.
- 6Choose a returned case ID.
- 7Retrieve the matching case details.
- 8Stop the app cleanly.
Choose the next small feature
You can now continue toward the proof-of-concept brief checker or take the same foundation in a different direction. Keep the next request small enough to test on its own.
- Let the user select a search result instead of copying its case ID.
- Display the most useful case fields in a readable layout.
- Add clear loading, empty, and error states.
- Preserve a direct path to the source material.
- Begin the next brief-checking step from public or hypothetical text.
Review the current prototype and the features that are already working: Descrybe connection, tool listing, concept search, and case details. Propose three small next features that would move it toward a proof-of-concept brief checker. Do not implement them yet. For each option, explain the user value, the files or components likely affected, the main risk, and the smallest acceptance test. Recommend which single feature we should build next.Before this becomes a real product
A successful local prototype is a learning milestone, not a production-readiness review. A shared or client-facing legal tool needs explicit decisions about users, permissions, per-user OAuth, secure token storage, confidential information, logging, retention, source review, testing, monitoring, and failure handling.
Keep the distinction clear and vibe coding becomes much more useful: it can help you explore an idea quickly while you preserve deliberate checkpoints for everything that carries legal, security, or operational risk.