메뉴
2Lines Software brand voice and style guide. Extends brand-voice-common with company-specific guidelines for all 2Lines content including proposals, documentation, marketing materials, and client communications.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/johncarpenter/knowledge-base --skill 2lines-brand-voice명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | 2lines-brand-voice |
| description | 2Lines Software brand voice and style guide. Extends brand-voice-common with company-specific guidelines for all 2Lines content including proposals, documentation, marketing materials, and client communications. |
| extends | brand-voice-common |
Brand voice and style guidelines for 2Lines Software. Use this skill when creating any content representing 2Lines — proposals, documentation, blog posts, client communications, and marketing materials.
Note: This skill extends
brand-voice-common. See that skill for general frameworks on tone adaptation, style enforcement, and terminology management.
| Use This | Not This | Notes |
|---|---|---|
| 2Lines Software | 2 Lines Software | No space between "2" and "Lines" |
| 2Lines | Two Lines, 2-Lines | Shorthand form, no space or hyphen |
| the 2Lines team | the 2Lines Software team | Use shorthand when "team" follows |
Capitalization: Always capitalize the "L" in "2Lines" — never "2lines" or "2LINES".
First mention: Use "2Lines Software" on first mention in formal documents, then "2Lines" thereafter.
If 2Lines Software were a person, they would be:
A seasoned technical partner who genuinely cares about your success. They've seen what works and what doesn't across many projects. They explain complex things clearly without being condescending, ask the right questions before diving in, and deliver what they promise. They're confident but never arrogant — the kind of expert who makes you feel smarter after every conversation.
| Audience | What They Care About | How to Address Them |
|---|---|---|
| CTOs / Technical Leaders | Architecture decisions, team capability, risk mitigation | Peer-to-peer, technical depth available but not assumed |
| Project Managers | Timelines, communication, deliverables, budget | Clear milestones, proactive updates, no surprises |
| Business Stakeholders | ROI, business outcomes, competitive advantage | Outcomes over outputs, business language |
| Audience | What They Care About | How to Address Them |
|---|---|---|
| Development Teams | Code quality, knowledge transfer, working alongside | Respectful collaboration, not "coming in to fix things" |
| Procurement / Legal | Risk, compliance, terms | Professional, thorough, patient with process |
We embed with your team, not just deliver and disappear. Your success is our success.
We build things that work, not things that are impressive for their own sake. Right-sized solutions.
You'll always know where things stand. No surprises, no jargon walls, no hidden agendas.
We've done this before. We know what works and what doesn't, and we share that knowledge freely.
The 2Lines voice adapts while staying recognizable:
| Context | Dial Up | Dial Down |
|---|---|---|
| Proposal / Sales | Confidence, expertise | Informality |
| Technical Documentation | Clarity, precision | Warmth |
| Client Slack / Email | Collaboration, approachability | Formality |
| Incident / Problem | Transparency, accountability | Confidence (acknowledge uncertainty) |
| Blog / Thought Leadership | Pragmatism, expertise | Sales language |
| Internal Communications | Directness, informality | Polish |
| Rule | 2Lines Standard |
|---|---|
| Oxford comma | Yes |
| Contractions | Use them — we're conversational |
| Headings | Sentence case |
| Numbers | Spell out one through nine, numerals for 10+ |
| Dates | Month DD, YYYY (January 15, 2025) |
| Time | 12-hour with AM/PM, include timezone when relevant |
| Percent | Use % symbol |
| Lists | No periods for fragments, periods for full sentences |
| Use This | Not This | Notes |
|---|---|---|
| 2Lines Software | 2 Lines, Two Lines | Company name |
| the team | resources | People, not resources |
| client | customer | We partner with clients |
| build | develop, engineer | Plain language preferred |
| timeline | ETA, delivery window | Clear and direct |
| trade-offs | pros and cons | More precise |
| scope | requirements (when informal) | Context-dependent |
Define or explain on first use when writing for non-technical audiences:
For technical audiences, use terms directly without over-explaining.
| Product/Service | Full Name | Shorthand | Notes |
|---|---|---|---|
| [placeholder] | [Full Product Name] | [Short form] | [Usage notes] |
Following the guidelines in brand-voice-common:
When reviewing content for 2Lines brand voice:
