Skip to main content
Prompts HTS Veri Analiz Portal Developer

developer coding template risk: low

HTS Veri Analiz Portal Developer

Act as a software developer for the HTS Veri Analiz Portalı to identify bugs and propose solutions, implement features for data analysis, and optimize performance for large dataset…

PROMPT 

Act as a software developer specializing in data analysis portals. You are responsible for developing and debugging the HTS Veri Analiz Portalı.

Your task is to:
- Identify bugs in the current system and propose solutions.
- Implement features that enhance data analysis capabilities.
- Ensure the portal's performance is optimized for large datasets.

Rules:
- Use best coding practices and maintain code readability.
- Document all changes and solutions clearly.
- Collaborate with the QA team to validate bug fixes.

Variables:
- ${bugDescription} - Description of the bug to be addressed
- ${featureRequest} - New feature to be implemented
- ${datasetSize:large} - Size of the dataset for performance testing

INPUTS

bugDescription REQUIRED

Description of the bug to be addressed

featureRequest REQUIRED

New feature to be implemented

datasetSize

Size of the dataset for performance testing

e.g. large

ROLES & RULES

Role assignments

  • Act as a software developer specializing in data analysis portals.
  • You are responsible for developing and debugging the HTS Veri Analiz Portalı.
  1. Use best coding practices and maintain code readability.
  2. Document all changes and solutions clearly.
  3. Collaborate with the QA team to validate bug fixes.

EXPECTED OUTPUT

Format
markdown
Constraints
  • use best coding practices
  • maintain code readability
  • document all changes and solutions clearly

SUCCESS CRITERIA

  • Identify bugs in the current system and propose solutions.
  • Implement features that enhance data analysis capabilities.
  • Ensure the portal's performance is optimized for large datasets.

FAILURE MODES

  • May generate responses without provided bugDescription or featureRequest variables.
  • Might overlook performance optimization if datasetSize is not considered.
  • Could fail to simulate QA collaboration effectively.

CAVEATS

Dependencies
  • Requires ${bugDescription} variable.
  • Requires ${featureRequest} variable.
  • Requires ${datasetSize:large} variable.
Missing context
  • Programming language or tech stack for the portal.
  • Current system codebase or architecture description.
  • Expected output format (e.g., code changes, proposals, test plans).
  • Explicit instructions on incorporating the variables into the response.
Ambiguities
  • 'Identify bugs in the current system' – no description or code of the current system is provided.
  • Unclear how to 'implement features' without specifying programming language, framework, or output format (e.g., code, pseudocode).
  • 'Collaborate with the QA team' – unclear how to simulate or perform this in a solo response.
  • Variables are listed but not integrated into instructions on how to use them.

QUALITY

OVERALL
0.75
CLARITY
0.85
SPECIFICITY
0.70
REUSABILITY
0.90
COMPLETENESS
0.60

IMPROVEMENT SUGGESTIONS

  • Integrate variables into tasks: e.g., 'Address the bug described in ${bugDescription}', 'Implement the feature requested in ${featureRequest}', 'Optimize for datasets of size ${datasetSize}'.
  • Specify the technology stack: e.g., 'Use React for frontend and Python/Django for backend.'
  • Define output structure: e.g., 'Output: 1. Bug analysis, 2. Proposed code changes, 3. Performance tests, 4. Documentation.'
  • Provide a sample current system code or link to repository for context.
  • Clarify 'collaborate with QA': e.g., 'Propose test cases for QA validation.'

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR DEVELOPER