added Health/Transparency; changed social link
This commit is contained in:
@@ -1,6 +1,11 @@
|
||||
---
|
||||
tags:
|
||||
- Writing
|
||||
categories:
|
||||
- Praxis
|
||||
- ML
|
||||
- Experience
|
||||
- Best Practices
|
||||
cssclasses:
|
||||
- table-wide
|
||||
- table-wrap
|
||||
@@ -10,7 +15,7 @@ description: |
|
||||
abstract: |
|
||||
This report presents practical methodologies and best practices for developing software using Cursor, an AI-assisted IDE. The paper details a structured workflow that emphasizes specification-driven development, comprehensive documentation practices, and systematic task management to maintain quality control when working with language models. Through detailed examples and rule configurations, it demonstrates how to leverage AI capabilities while mitigating common pitfalls such as redundant code generation and context limitations. The methodology presented includes comprehensive PRD (Product Requirement Document) creation, specification adherence checks, and task breakdown systems that ensure alignment between human intent and AI execution. This guide serves as a practical reference for developers seeking to effectively integrate AI tools into their software development workflow while maintaining project integrity and scalability.
|
||||
|
||||
lang: de
|
||||
lang: en
|
||||
date: 2025-06-26
|
||||
authors:
|
||||
- name: Nicole Dresselhaus
|
||||
@@ -266,7 +271,6 @@ one‑sentence feature description plus any additional Q&A with the stakeholder.
|
||||
it in _Open Questions_.
|
||||
4. After questions are answered reply exactly: Ready to generate the PRD.
|
||||
5. On a user message that contains only the word "go" (case‑insensitive):
|
||||
|
||||
- Generate /tasks/<feature>/PRD.md following _Output_ spec.
|
||||
- Reply: <feature>/PRD.md created – review it.
|
||||
|
||||
@@ -327,19 +331,16 @@ Every specification should include:
|
||||
```
|
||||
|
||||
2. **Scope and Boundaries**
|
||||
|
||||
- What is included/excluded
|
||||
- Dependencies on other specifications
|
||||
- Relationship to other components
|
||||
|
||||
3. **Detailed Requirements**
|
||||
|
||||
- Structured by logical sections
|
||||
- Clear, unambiguous language
|
||||
- Examples where helpful
|
||||
|
||||
4. **Error Handling**
|
||||
|
||||
- How errors should be handled
|
||||
- Fallback behaviors
|
||||
- Edge cases
|
||||
|
Reference in New Issue
Block a user