What to Know Before Asking or Answering a Puzzle on Puzzling Stack Exchange

Puzzling Stack Exchange is a Q&A site for people who create, solve, and study puzzles, and it works best when questions are self-contained and answers show their reasoning. Before you post, decide whether you are asking a puzzle (you know the answer and want solvers to find it) or asking about a puzzle (you are stuck and want help). The site's Help Center and Tour are the authoritative places to check current rules, and the community's votes and comments are how quality gets sorted out.

Asking a puzzle

A good puzzle question gives solvers everything they need without giving away the solution.

• State the puzzle clearly. Include the full setup, the exact question, and any constraints. If a solver cannot attempt it from your post alone, it is not ready.
• Use tags that match the puzzle. The site's tag list includes riddle, mathematics, logical-deduction, word, knowledge, enigmatic-puzzle, visual, wordplay, pattern, cipher, chess, strategy, optimization, graph-theory, topology, number-theory, and more. Pick the ones that describe the actual solving skill required, not just the theme.
• Decide whether it is a puzzle or a question about a puzzle. "Here is a riddle, what is the answer?" is a puzzle. "I found this riddle and I don't understand the accepted answer" is a question about a puzzle. They are received differently.
• Avoid trivia disguised as a puzzle. If the only way to solve it is to already know one fact, say so with the knowledge tag, or reconsider whether it belongs.
• Do not bury the puzzle in a story. Flavor text is fine, but the solvable content must be unambiguous.

If you are unsure whether your puzzle is fair, the Help Center and Meta are where format and scope questions get answered.

Answering a puzzle

The most common reason an answer gets downvoted is that it states a conclusion without showing how it was reached.

• Explain the reasoning, not just the result. Walk through the steps a solver would take. If you used a program, say what it did and what it found.
• Match the puzzle's constraints. If the puzzle says no computers, a brute-force answer is not a valid solution even if the number is right.
• Handle partial answers honestly. If you have a partial solution, say which parts are proven and which are guesses. Partial progress is often welcome, but it should be labeled.
• Use spoiler formatting when the puzzle is still fresh. On Puzzling, answers that reveal the solution are commonly hidden behind spoiler markup so readers can choose when to see it. Check the Help Center for the current formatting.
• Do not edit the puzzle to fit your answer. If you think the puzzle is flawed, say so in your answer or in a comment rather than silently changing the rules.

How quality is judged

The site does not have editors approving each post. Quality is signaled by votes, comments, and accepted answers.

If your post gets comments asking for clarification, edit the post rather than arguing in the comments. Editing is the normal way to fix a question or answer.

Common pitfalls

• Puzzles that depend on a private fact. If only you could know the answer, the puzzle is not solvable by others.
• Ambiguous wording. Multiple valid answers usually mean the puzzle needs tightening, not that solvers are wrong.
• Answers that are just a link. Link-only answers are fragile and usually downvoted; summarize the relevant content in the answer itself.
• Ignoring the tag's expectations. A logical-deduction puzzle is expected to be solvable by deduction, not by guessing.
• Arguing with downvotes. Votes are not a debate; use comments and edits to improve the post.

Where to check the rules

The Tour gives a quick overview of how the site works. The Help Center covers asking, answering, formatting, and what is on-topic. Meta is where policy discussions and site-specific conventions live. Because rules and formatting conventions can change, treat those pages as the current source rather than any summary, including this one.