You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After a lot of tinkering and videos and errors, we've bitten the bullet and attacked a real production level .Net solution with spec link. Ambitious, huh?
One of the conclusions was that once we get to tasks and implementations two things are obvious:
1 We need our own ps scripts (no linux, forbidden and excommunicated) to create solutions, provide scaffolding, et.
More important:
2 We need our own prompts to conduct and validate properly the input and generate in consequence.
And
3 Markdown only can get us this far. We need and have Xaml templates, Yaml declarations, Classes and lots of documents and formats. Do I need to just make them accessible to spec kit workspace? No metabases or such, right?
I think documents and scripts only need to be available for the prompts, but the prompts also validate and do more work. Any suggestions?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
After a lot of tinkering and videos and errors, we've bitten the bullet and attacked a real production level .Net solution with spec link. Ambitious, huh?
One of the conclusions was that once we get to tasks and implementations two things are obvious:
1 We need our own ps scripts (no linux, forbidden and excommunicated) to create solutions, provide scaffolding, et.
More important:
2 We need our own prompts to conduct and validate properly the input and generate in consequence.
And
3 Markdown only can get us this far. We need and have Xaml templates, Yaml declarations, Classes and lots of documents and formats. Do I need to just make them accessible to spec kit workspace? No metabases or such, right?
I think documents and scripts only need to be available for the prompts, but the prompts also validate and do more work. Any suggestions?
Beta Was this translation helpful? Give feedback.
All reactions