# Design document & wireframes

**URL:** <https://forum.cursor.com/t/design-document-wireframes/49086>\
**Category:** Help\
**Created:** [February 8, 2025, 12:58pm UTC](https://forum.cursor.com/t/design-document-wireframes/49086 "2025-02-08T12:58:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![macken04](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/macken04/32/25260_2.png) [@macken04](https://forum.cursor.com/u/macken04)\
**Post date:** [February 8, 2025, 12:58pm UTC](https://forum.cursor.com/t/design-document-wireframes/49086/1 "2025-02-08T12:58:35Z")

</div>

Hello community,

I am new to Cursor and on my second application, which is a iOS app, I will work between Curson and Xcode.

Based on learnings from my first web app, I have built a much more comprehensive design document. This includes;

Goals of the application  
Key requirements  
Technical requirement (backend, data storage etc)  
Detail on design principals (ui)  
Page by page design brief  
Text based ui wireframe  
Detailed design requirements inc specific stylings

All of this is quite detailed, but more understanding is having this as reference documentation for the project will greatly assist with the build as I want to try build as much with LLM assistance as possible.

Can you please advise how I would go about configuring this within Cursor?

---

<div class="post-metadata">

**Author:** ![danperks](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/danperks/32/19087_2.png) [@danperks](https://forum.cursor.com/u/danperks)\
**Post date:** [February 17, 2025, 7:31pm UTC](https://forum.cursor.com/t/design-document-wireframes/49086/2 "2025-02-17T19:31:35Z")

</div>

You can structure all of this documentation using Project Rules in the `.cursor/rules` directory - this is the most comprehensive way to keep everything organized and accessible to the AI

Here’s how I’d break it down:

1. Create separate rule files for each section (goals, requirements, design, etc)
2. Use glob patterns to match iOS-specific files
3. Reference your wireframes and detailed specs using @file syntax

For the iOS-specific stuff, you can use @Docs to include any relevant Apple documentation that you want the AI to reference

Check out our docs on Project Rules for the full setup guide: [Cursor – Rules for AI](https://docs.cursor.com/context/rules-for-ai)

And here’s how to configure custom docs: [Cursor – @Docs](https://docs.cursor.com/context/@-symbols/@-docs)

---

<div class="post-metadata">

**Author:** ![macken04](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/macken04/32/25260_2.png) [@macken04](https://forum.cursor.com/u/macken04)\
**Post date:** [February 17, 2025, 8:03pm UTC](https://forum.cursor.com/t/design-document-wireframes/49086/3 "2025-02-17T20:03:18Z")

</div>

Thanks mate - I’ve broken out all the documentation now. Have the master design document and have broken down each component part into a design document in a logical order. First part of the build done - will read the details you’ve shared and share any questions if I have them

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [June 18, 2026, 10:28am UTC](https://forum.cursor.com/t/design-document-wireframes/49086/4 "2026-06-18T10:28:26Z")

</div>

Closed on June 18, 2026, 10:28am UTC