'hn' 검색 결과

Plan technology strategy and engineering team growth with frameworks for technical debt, hiring, architecture decisions, and vendor evaluation. Use Python tools and decision templates to prioritize improvements, structure teams, and track engineering performance.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prioritizing technical debt reduction
• Planning hiring and engineering team structure
• Comparing technologies and vendors

Plan technology investments and engineering team growth using structured assessments. Evaluate technical debt, compare building versus buying, document architecture choices, and define engineering health metrics to produce prioritized plans grounded in costs, risks, and business needs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prioritize technical debt fixes by impact and effort
• Plan engineering hiring, timing, and budget
• Compare building internally with buying a service

Interact with Hacker News (news.ycombinator.com) — browse top, new, and best stories, read item details and comment threads, look up user profiles, and search posts via Algolia. Use this skill whenever the user mentions Hacker News, HN, YCombinator news, ycombinator.com, news.ycombinator.com, wants to browse tech news, read HN discussions, search HN posts, or look up HN users. Also trigger when the user pastes an HN URL (e.g. news.ycombinator.com/item?id=12345). Keywords: Hacker News, HN, YC, ycombinator, tech news, Show HN, Ask HN, HN front page.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

"Apply Sociotechnical Systems Theory to analyze and design work systems through joint optimization of social and technical subsystems. Use this skill when the user needs to diagnose why a technology implementation disrupted work practices, design IT-enabled work systems that balance human and technical needs, or when they ask 'why did this system hurt productivity despite being technically sound', 'how do we design work around new technology', or 'why are people resisting this technically superior system'.".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Fetch and send Hacker News front-page posts on demand. Use when the user asks for HN, says 'hn', 'pull HN', 'hn 10', or specifies a topic like 'hn health', 'hn hacking', or 'hn tech'. Sends N (default 5) posts as individual messages with Title + Link. Exclude crypto.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Tune vector indexes, which organize data for similarity searches, to balance speed, memory use, and missed matches. Choose index types, adjust HNSW settings, and assess compression options using benchmarks with real queries.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reduce latency in similarity searches
• Tune HNSW settings to reduce missed matches
• Compare compression options for lower memory use

Writes and rewrites text in Simplified Technical English (ASD-STE100), a controlled language for clear technical documentation. Use when the user asks for STE, Simplified Technical English, controlled language, or plain technical writing, and when the user asks to write, rewrite, review, or check technical documentation, procedures, manuals, instructions, warnings, or reports.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build a Hacker News + Reddit launch playbook for developer-tools and community-led products during PRD v0.9 Go-to-Market. Triggers on requests to plan HN/Reddit launch, "Show HN" post, community launch, or when user asks "HN launch", "Show HN", "Reddit launch", "launch on /r/SaaS", "Product Hunt vs HN", "community launch", "developer launch". Outputs GTM-* with Type=Channel-HN / Type=Channel-Reddit entries with timing, title, story angle, and engagement plan.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Hacker News post crafter — given a product, feature, or story produces a ready-to-post HN submission (title ≤80 chars, no marketing), honest body text with technical depth, no outbound links, predicted reception analysis, and comment-response templates for likely pushback. Use when asked to "write an HN post", "craft a Show HN", "prepare our Hacker News launch", or "help me post on HN".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Technical research methodology with YAGNI/KISS/DRY principles. Phases: scope definition, information gathering, analysis, synthesis, recommendation. Capabilities: technology evaluation, architecture analysis, best practices research, trade-off assessment, solution design. Actions: research, analyze, evaluate, compare, recommend technical solutions. Keywords: research, technology evaluation, best practices, architecture analysis, trade-offs, scalability, security, maintainability, YAGNI, KISS, DRY, technical analysis, solution design, competitive analysis, feasibility study. Use when: researching technologies, evaluating architectures, analyzing best practices, comparing solutions, assessing technical trade-offs, planning scalable/secure systems.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Turn a product requirements document for a major development initiative into a technical architecture specification, including a Mermaid system diagram, major features, supporting technologies, technical value, and a rough size estimate.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning product requirements into a technical architecture
• Visualizing system layers and data flows
• Identifying services and infrastructure needed for features

Map attacker behaviors and indicators of compromise, or traces of an intrusion, to MITRE ATT&CK techniques. Build coverage heatmaps, compare threat groups, and identify monitoring gaps to guide detection improvements and threat intelligence reporting.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Mapping attacker behaviors and intrusion traces to ATT&CK techniques
• Visualizing detection coverage with ATT&CK Navigator
• Identifying attack techniques missing from monitoring

Map threat groups and their attack techniques to MITRE ATT&CK, a catalog of adversary behavior. Generate Navigator visualization files, compare groups, and overlay detection coverage to identify gaps that can guide defensive planning.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Profiling the attack techniques used by a specific threat group
• Comparing techniques across multiple threat groups
• Finding detection gaps against a target adversary

Improve resumes for software engineering, technical product management, data, and DevOps roles. Organize technical skills, connect achievements to business results, and highlight projects in a format suited to applicant tracking systems, software used to process job applications, and recruiters.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Organize technical skills for a target role
• Rewrite experience to show technical and business impact
• Choose projects to highlight during a career change

Audit a website’s technical foundations for search engines and AI services. Check crawler access, indexing, security, mobile usability, speed, and server-rendered content, then produce a scored Markdown report with prioritized findings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check whether AI crawlers can access key pages
• Find content missing from the initial HTML
• Review page speed and mobile usability

Summarize popular Hacker News stories or find discussions on a specific topic. Get article highlights, scores, comment counts, and recurring discussion themes, including agreement, criticism, and related debates.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing the top ten Hacker News stories
• Summarizing an article and its discussion
• Finding Hacker News discussions on a topic

Create a technical design document before implementation by answering questions about the problem, scope, architecture, risks, and delivery plan. The skill adjusts sections to project size and covers security, testing, monitoring, and recovery where relevant.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Documenting the design of a new feature
• Planning an external service integration
• Preparing a system migration proposal

Turn a feature specification into a technical implementation plan. Organizes technology choices, research decisions, data models, and interface agreements into project files, while checking that the design follows the project's documented principles.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create a technical plan from a feature specification
• Resolve open questions about technology choices
• Document data models and external interfaces

Triage technical SEO findings from Ahrefs Site Audit (and similar crawlers) by SEO impact, not just severity. Use this skill when reviewing crawl results, prioritizing technical fixes, scoping a technical SEO sprint, or after running any site-wide crawl. Triggers on site audit results, technical fix list, crawl errors, technical SEO triage, prioritize technical issues, what should we fix first, broken links, redirect chains. Also triggers when a long list of crawler issues is creating decision paralysis.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, architecture rot, and low-value tests. Ranks findings by impact and refactor effort into a report at .turbo/technical-debt.md. Use when the user asks to "assess technical debt", "find technical debt", "review technical debt", "what should we refactor", "find refactoring candidates", "where is the code rot", "what's our worst code", "find low-value tests", or "which tests can we delete". Analysis-only — does not modify code.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

🇺🇸 Open-Source Marketing & GitHub Stars Growth System — Decision framework for each growth stage. Pre-launch readiness → Show HN / Reddit / Product Hunt launch → 6-month growth loop. README rules, KOL outreach, dev-content matrix (dev.to / Zenn), anti-star-farming. Built from taking AFFiNE 0 → 60K stars. 🇨🇳 开源营销与 GitHub Star 增长系统 — 每个增长阶段的决策框架。Pre-launch 就绪 → Show HN / Reddit / Product Hunt 发布 → 6 个月增长循环。README 规则、KOL 合作、开发者内容矩阵（dev.to / Zenn）、防刷 star。提炼自 AFFiNE 0 → 60K star 实战。 🇯🇵 オープンソースマーケティング＆GitHub スター成長システム — 各成長段階の意思決定フレームワーク。Pre-launch → Show HN / Reddit / Product Hunt → 6ヶ月成長ループ。READMEルール、KOL連携、開発者コンテンツマトリックス。 🇰🇷 오픈소스 마케팅 & GitHub 스타 성장 시스템 — 각 성장 단계별 의사결정 프레임워크. 사전 출시 → Show HN / Reddit / Product Hunt → 6개월 성장 루프. README 규칙, KOL 아웃리치, 개발자 콘텐츠 매트릭스. Triggers: "open source marketing" | "GitHub stars" | "star growth" | "Show HN" | "Hacker News launch" | "OSS launch" | "developer marketing" | "Reddit launch" | "dev.to" | "open source growth" | "开源营销" | "GitHub star 增长" | "开源发布" | "Show HN 怎么发" | "开发者营销" | "オープンソース" | "오픈소스 성장"

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

"Apply the TPACK framework to evaluate and design technology-integrated instruction at the intersection of technological, pedagogical, and content knowledge. Use this skill when the user needs to assess teacher readiness for technology integration, design professional development for ed-tech, or evaluate whether technology use is pedagogically grounded — even if they say 'how to integrate technology in teaching', 'ed-tech evaluation', or 'teacher technology competency'.".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

분산된 에이전트 기억을 AgentDB로 통합하고 SQLite와 Markdown 데이터 이전, 의미가 비슷한 정보 검색, 에이전트 간 기억 공유를 설계합니다.

• 분산된 에이전트 기억을 통합합니다
• SQLite와 Markdown 데이터를 이전합니다
• 의미가 비슷한 저장 정보를 검색합니다