Repository navigation
feature: UI spec prompt for the overdue inbound dashboard card demo - #5
Closed
matthewguerra-cog wants to merge 1 commit into
Closed
matthewguerra-cog wants to merge 1 commit into
matthewguerra-cog wants to merge 1 commit into
Conversation
…d demo Co-Authored-By: Matthew Guerra <matthew.guerra@cognition.ai>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
✨ Description of Change
Link to GitHub issue or Jira ticket: n/a (spec-driven-development demo material)
Description:
Adds
docs/demo/ui-spec-prompt.md— the prompt used in the demo to have Devin produce a UI spec (as opposed to the OpenAPI contract inopenapi/specs/shipment-exceptions-api.yaml), plus the reasoning for why that prompt is shaped the way it is.Documentation only: one new markdown file, no code, config, or spec changes.
The feature the prompt targets is an "Overdue inbound" card on the warehouse dashboard, fed by the
GET /api/shipments/exceptions/overdueendpoint that already exists on this branch — so it is deliberately UI-only, with no backend query, domain change, or migration. The prompt points at the repo's real conventions so the generated spec is grounded rather than generic:openboxes.dashboardConfigingrails-app/conf/runtime.groovy(enabled/title/info/type/graphType/endpoint, and dashboards list widgets bywidgetId+order)src/js/components/dashboard/(NumberCard,TableCard,NumbersTableCard,GraphCard)react.dashboard.*keys ingrails-app/i18n/messages.propertiesUserService.getDashboardConfigThe file contains both a short version of the prompt (for presenting live) and a fuller version (for a more predictable result), and it asks for numbered acceptance criteria in the style of
openapi/specs/shipment-exceptions-acceptance-criteria.mdso a UI spec — which no linter can check — still ends up verifiable by a Playwright test undercharacterization/tests/.Devin-Org: engineering
Link to Devin session: https://app.devin.ai/sessions/c3eddd41a03445f3afc7922b3579bddc
Requested by: @matthewguerra-cog
Devin Review
44749f2