prompt engineering

Engineering Community

Skill notes

1. Structure with XML Tags

Use XML tags to create clear, parseable prompts: Benefits: Clarity: Separates context, instructions, and examples Accuracy: Prevents model from mixing up sections Flexibility: Easy to modify individual parts

2. Control Output Shape

Specify explicit constraints on length, format, and structure:

3. Prevent Scope Drift

Explicitly constrain what the model should NOT do:

4. Handle Ambiguity Explicitly

Prevent hallucinations and overconfidence:

5. Long-Context Grounding

For inputs >10k tokens, add re-grounding instructions:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@CodeAlive-AI · MIT
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview prompt-engineering.preview
# 2. Control Output Shape

<output_spec>
- Default: 3-6 sentences or ≤5 bullets
- Simple yes/no questions: ≤2 sentences
- Complex multi-step tasks:
  - 1 short overview paragraph
  - ≤5 bullets: What changed, Where, Risks, Next steps, Open questions
- Use Markdown with headers, bullets, tables when helpful
- Avoid long narrative paragraphs; prefer compact structure
</output_spec>

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.