owl-listener/ai-design-skills

constraint-specification

Defining output format, length, tone, and content boundaries within prompts.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/owl-listener/ai-design-skills --skill constraint-specification

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Constraint Specification

Constraints are the rules that shape AI output — what format to use, how long to be, what to include, what to exclude. Well-specified constraints produce predictable, useful outputs. Vague constraints produce inconsistent results.

Types of Constraints

Format constraints:

  • Output structure (JSON, markdown, plain text, bullet points, prose)
  • Section headings and organisation
  • Required fields and optional fields
  • Data types and schemas

Length constraints:

  • Word count ranges (not exact numbers — models are bad at counting)
  • Section length proportions ("spend 60% on analysis, 40% on recommendations")
  • Minimum and maximum bounds
  • Conciseness directives ("be brief" vs. "be thorough")

Content constraints:

  • Topics to include and exclude
  • Required information elements
  • Prohibited content
  • Source restrictions (only use provided context, don't use external knowledge)

Tone constraints:

  • Formality level
  • Emotional register
  • Audience-appropriate language
  • Voice and style guidelines

Quality constraints:

  • Accuracy requirements ("cite sources", "flag uncertainty")
  • Completeness requirements ("address all aspects of the question")
  • Originality requirements ("don't repeat the question back")
  • Actionability requirements ("every recommendation must be implementable")

Writing Effective Constraints

  • Be specific: "Keep responses under 200 words" beats "be concise"
  • Prioritise: When constraints conflict, state which wins. "Accuracy over brevity."
  • Provide examples: Show what a constrained output looks like
  • Test boundaries: What happens at the edge of each constraint?
  • Separate hard and soft constraints: Hard constraints must always be met. Soft constraints are preferences.

Constraint Interactions

Constraints interact and can conflict:

  • "Be thorough" vs. "Keep it under 100 words"
  • "Be creative" vs. "Follow this exact format"
  • "Be helpful" vs. "Don't give medical advice"

Resolve conflicts explicitly in the prompt. Don't make the model guess which constraint takes priority.

Design Artefacts

  • Constraint specification documents per output type
  • Constraint priority hierarchies
  • Constraint test cases (inputs designed to stress each constraint)
  • Constraint violation examples (what bad looks like)
  • Constraint evolution logs (how constraints changed and why)
같은 저장소의 Skills

더 많은 Skills

모든 Skills