Atlas E74243keac

Emergent Help

Begin with your basic business goal, idea, and desired features 

Use plain language to describe what you want to build.

 Based on Emergent Agent capabilities, structure your initial prompt with:

**Business Goal:** [Clear, simple description]
**Core Features:** [List 3-5 main features]
**Target Users:** [Who will use this]
**Success Criteria:** [How you'll measure success]





 - Emergent Agents respond better to clear and concise instructions.

 - Explain WHY features are important, not just WHAT you want.

 - Tell the Emergent Agent what TO do instead of what NOT to do.

 Instead of "Create a dashboard," use "Create a comprehensive analytics dashboard with interactive features and modern design principles".

Agent will plan the task and ask question regarding planning and prioritization.

Always guide the agent as per your use case.

If you wish to brainstorm with the agent, use: 

Discuss potential challenges and solutions upfront.

"Start building based on what we discussed".

Implement 1-2 features maximum per development cycle.

Complete each feature fully before moving to the next.

Test each increment thoroughly before proceeding.

 example "Include hover states, transitions, and micro-interactions".

 example "Go beyond the basics to create a fully-featured implementation".

 example "Apply modern design principles: hierarchy, contrast, balance, and movement".

 Address bugs in dedicated messages, implement new features in separate messages.

 Complete error resolution before requesting new features.

Avoid Interrupting Emergent Agent Mid-Process

Emergent Agents follow instructions precisely - interrupting can create unfinished features.

Let the Emergent Agent complete its current task before providing new directions.

"Please finish your current task, then we'll discuss [new topic]".

Always test the application in your browser before reporting issues.

Document specific error messages, browser console errors, and steps to reproduce.

Include screenshots or screen recordings when helpful.

Ask the Emergent Agent to test the frontend itself if you're missing errors.

The Emergent Agent can identify issues not visible in the UI that might be causing problems.

Provide browser developer console logs if available.

"Test all interactive elements and validate responsive design".

"Review the code for potential issues and suggest improvements".

Push code to GitHub after each major feature completion.

When approaching context limits, always push to GitHub first.

 Ask the Emergent Agent to create a comprehensive summary including:
 

Use rollback tools when approaching context limits or want to go back to a working checkpoint in code.

It's better to rollback to a working state than to debug extensively corrupted code.

Emergent Agents can occasionally make complex mistakes due to their advanced capabilities.

Provide the Emergent Agent with the implementation summary from the previous session.

"Continue from where we left off based on this summary".

 You can also add any specific changes or directions that you want the agent to adhere or first respond to.

Reference the specific features that were in progress.

Avoid major scope changes mid-development - they can break existing functionality.

Minor deviations are acceptable, but major pivots require starting fresh.

Complete the current version before considering significant changes.

If you want to fundamentally change the application concept.

When technical architecture needs complete overhaul.

Request specific performance improvements: 

"Optimize for loading speed and smooth interactions".

"Implement using current web development best practices".

 - Focus on what you want, not what you don't want.

 - Encourage comprehensive, high-quality implementations.

 - Validate each feature before proceeding.

 - Don't mix bug fixes with new feature requests.

Starting to build without clear business requirements.

Sharing too much technical requirements, that is not inline with agent’s capabilities.

Mixing error reports with new feature requests.

Changing scope dramatically mid-development.

Not testing features before reporting bugs.

Forgetting to commit working code to GitHub.

Not providing implementation summaries when clearing context.

 Modern AI agents are exceptionally capable but require precise, thoughtful prompting to deliver optimal results. The investment in clear communication and structured development processes will yield significantly better applications.

For any questions or assistance, feel free to email us at 

Development Guide!

Guide To Prompt